biztrac. BETA
COMPANY REGISTER PROFILE
929392000 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
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 2025 NOK 1.9m
Operating profit NOK 1.8m
Equity NOK 1.5m
Incorporated 2022
Share capital NOK 300,000

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 2025 financial year, show NOK 1.9m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +0 %
Operating profit
NOK 1.8m
▲ +0 %
Equity
NOK 1.5m
▼ −10 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
7.11
Very good
Current assets ÷ current liabilities
Profitability
55.2%
Very good
Return on total assets
Solidity
70.1%
Very good
Equity as a share of total capital

Who owns F.N.H EIENDOM AS?

F.N.H EIENDOM AS
NOK 1.9m rev. · NOK 1.8m 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 1.9m in 2025.

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

Report a problem

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