BIZTRAC BETA
Graphic design and visual communication activities

SPOON AS

Org. no. 989389874 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 74.1m
Operating profit NOK −1.2m
Equity NOK 15.6m
Incorporated 2006
Employees 27
Share capital NOK 143,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

SPOON AS is registered as a limited company in Oslo, Oslo with organisation number 989389874. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2006 and has 27 registered employees. Registered share capital is NOK 143,000, divided into 1425 shares. The company's stated purpose is: “Selskapets formål er grafiske tjenester og annen virksomhet som ligger under dette. Selskapet skal også utvikle nye redaksjonelle konsepter, samt kursvirksomhet og undervisning innen journalistikk og grafisk design.”. The most recent filed accounts, for the 2024 financial year, show NOK 74.1m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 74.1m
Operating profit
NOK −1.2m
Equity
NOK 15.6m
Est. value
NOK 85.4m

Financial health · 2024

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.5%
Very good
Equity as a share of total capital

Who owns SPOON AS?

SPOON AGENCY AB
SPOON AS
NOK 74.1m rev. · NOK −1.2m profit

SPOON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPOON AS

Who owns SPOON AS?

SPOON AGENCY AB is the largest registered owner, with 100.0%.

What is the revenue of SPOON AS?

SPOON AS had revenue of NOK 74.1m in 2024.

Who is the general manager of SPOON AS?

Anders Waage is registered as general manager of SPOON AS.

Where is SPOON AS based?

SPOON AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.