BIZTRAC BETA
Other non-specialised retail sale

ERATO AS

Org. no. 838236642 Limited company (AS) Nannestad Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK −51,000
Equity NOK −231,000
Incorporated 1986
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−231k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−51k kr).

ERATO AS is registered as a limited company in Nannestad, Akershus with organisation number 838236642. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 1986. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Trykking, handelsvirksomhet - herunder import og agenturvirksomhet og transport, samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK −51,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK −51,000
Equity
NOK −231,000

Financial health · 2024

Liquidity
5.35
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-33.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ERATO AS?

MORTEN BYRBOTTEN ANDREASSEN
ERATO AS
NOK 1.6m rev. · NOK −51,000 profit

ERATO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ERATO AS

Who owns ERATO AS?

MORTEN BYRBOTTEN ANDREASSEN is the largest registered owner, with 50.0%.

What is the revenue of ERATO AS?

ERATO AS had revenue of NOK 1.6m in 2024.

Who is the general manager of ERATO AS?

Terje Andreassen is registered as general manager of ERATO AS.

Where is ERATO AS based?

ERATO AS has its business address in Holter.

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.