BIZTRAC BETA
Rental and operating of own or leased real estate

NOFI EIENDOM AS

Org. no. 921485700 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 2.9m
Equity NOK 4.2m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NOFI EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 921485700. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å legge til rette for næringsutvikling gjennom å eie og drifte næringsarealer og næringsbygg.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 2.9m in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 2.9m
Equity
NOK 4.2m
Est. value
NOK 7.1m

Financial health · 2025

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns NOFI EIENDOM AS?

NOFI AS
NOFI EIENDOM AS
NOK 6.9m rev. · NOK 2.9m profit

NOFI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NOFI EIENDOM AS own?

NOFI EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NOFI EIENDOM AS

Who owns NOFI EIENDOM AS?

NOFI AS is the largest registered owner, with 100.0%.

What is the revenue of NOFI EIENDOM AS?

NOFI EIENDOM AS had revenue of NOK 6.9m in 2025.

Where is NOFI EIENDOM AS based?

NOFI EIENDOM AS has its business address in Kvaløya.

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.