biztrac. BETA
COMPANY REGISTER PROFILE
921693125 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ERR-NOR AS

Org. no. 921693125 Limited company (AS) Frogn Incorporated 2018 Active
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK −784,000
Incorporated 2018
Share capital NOK 300,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−784k kr).

ERR-NOR AS is registered as a limited company in Frogn, Akershus with organisation number 921693125. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Næringsaktivitet, kjøp og salg av aksjer og selskaper, annen handelsrelatert virksomhet, samt eie aksjer i andre selskaper med alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −14,000
▼ −226 %
Equity
NOK −784,000
▼ −1 %
Est. value
NOK 225,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.4%
Not satisfactory
Return on total assets
Solidity
-251.1%
Weak
Equity as a share of total capital

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

Who owns ERR-NOR AS?

ERR-NOR AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about ERR-NOR AS

Who owns ERR-NOR AS?

Anders Wilhelm Rosenlund is the largest registered owner, with 33.3%.

What is the revenue of ERR-NOR AS?

ERR-NOR AS had revenue of NOK 0 in 2025.

Who is the general manager of ERR-NOR AS?

Anders Wilhelm Rosenlund is registered as general manager of ERR-NOR AS.

Where is ERR-NOR AS based?

ERR-NOR AS has its business address in Drøbak.

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

Report a problem

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