biztrac. BETA
COMPANY REGISTER PROFILE
920221289 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

AS NORDNES-EIENDOM

Org. no. 920221289 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −40,000
Equity NOK 429,000
Incorporated 2017
Share capital NOK 48,000

Signals

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

AS NORDNES-EIENDOM is registered as a limited company in Bergen, Vestland with organisation number 920221289. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 48,000, divided into 9666 shares. The company's stated purpose is: “Kjøp, utvikling og utleie av fast eiendom. Selskapet kan og foreta investeringer i andre selskaper med tilsvarende formål.”.

Former names: SIGNOR EIENDOM AS

Key figures · 2025

Operating profit
NOK −40,000
▲ +67 %
Equity
NOK 429,000
▼ −54 %
Est. value
NOK 36.1m

Financial health · 2025

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.7%
Not satisfactory
Equity as a share of total capital

Who owns AS NORDNES-EIENDOM?

AS NORDNES-EIENDOM
· NOK −40,000 profit

AS NORDNES-EIENDOM has 2 registered shareholders:

All shareholders and roles →

Which companies does AS NORDNES-EIENDOM own?

AS NORDNES-EIENDOM holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AS NORDNES-EIENDOM

Who owns AS NORDNES-EIENDOM?

BAKKE HOLDINGS AS is the largest registered owner, with 66.7%.

Where is AS NORDNES-EIENDOM based?

AS NORDNES-EIENDOM has its business address in Bergen.

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.