biztrac. BETA
COMPANY REGISTER PROFILE
824000522 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
In liquidation UPDATED 03.10.2026
⚠FORNEBU BRYGGE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

FORNEBU BRYGGE AS

Org. no. 824000522 Limited company (AS) Oslo Incorporated 2019 In liquidation
Ownership graph ↗
Operating profit NOK −202,000
Equity NOK 2.2m
Incorporated 2019
Share capital NOK 90,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−202k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FORNEBU BRYGGE AS is registered as a limited company in Oslo, Oslo with organisation number 824000522. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 90,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer, immaterielle aktiva og andre eierandeler i andre selskaper og foretak, samt all annen virksomhet som hermed står i forbindelse.”.

Former names: START UP 514 AS, SJØ FORNEBU AS

Key figures · 2025

Operating profit
NOK −202,000
▲ +89 %
Equity
NOK 2.2m
▲ +2056 %

Financial health · 2025

Liquidity
27.24
Very good
Current assets ÷ current liabilities
Profitability
-8.4%
Not satisfactory
Return on total assets
Solidity
96.3%
Very good
Equity as a share of total capital

Who owns FORNEBU BRYGGE AS?

FORNEBU BRYGGE AS
· NOK −202,000 profit

FORNEBU BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FORNEBU BRYGGE AS

Who owns FORNEBU BRYGGE AS?

SJØ AS is the largest registered owner, with 100.0%.

Where is FORNEBU BRYGGE AS based?

FORNEBU BRYGGE 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 03.10.2026.

Report a problem

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