BIZTRAC BETA
Rental and operating of own or leased real estate

F.N.H EIENDOM AS

Org. no. 929392000 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 226,000
Operating profit NOK −236,000
Equity NOK 300,000
Incorporated 2022
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−236k kr).

F.N.H EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 929392000. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Eie, forvalte og utleie fast eiendom og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 226,000 in revenue and NOK −236,000 in operating profit.

Key figures · 2024

Revenue
NOK 226,000
Operating profit
NOK −236,000
Equity
NOK 300,000
Est. value
NOK 274,000

Financial health · 2024

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

Who owns F.N.H EIENDOM AS?

BILNETT AS
F.N.H EIENDOM AS
NOK 226,000 rev. · NOK −236,000 profit

F.N.H EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about F.N.H EIENDOM AS

Who owns F.N.H EIENDOM AS?

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

What is the revenue of F.N.H EIENDOM AS?

F.N.H EIENDOM AS had revenue of NOK 226,000 in 2024.

Where is F.N.H EIENDOM AS based?

F.N.H EIENDOM AS has its business address in Drammen.

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.