BIZTRAC BETA
Rental and operating of own or leased real estate

FONNES BIL EIENDOM AS

Org. no. 815343492 Limited company (AS) Austrheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 366,000
Operating profit NOK 138,000
Equity NOK −327,000
Incorporated 2015
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−327k kr).

FONNES BIL EIENDOM AS is registered as a limited company in Austrheim, Vestland with organisation number 815343492. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 50,000, divided into 100000 shares. The company's stated purpose is: “Investering i og drift av fast eiendom, eiendomsutvikling samt deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 366,000 in revenue and NOK 138,000 in operating profit.

Key figures · 2025

Revenue
NOK 366,000
Operating profit
NOK 138,000
Equity
NOK −327,000
Est. value
NOK 667,000

Financial health · 2025

Liquidity
263.77
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-19.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FONNES BIL EIENDOM AS?

STRANDHAUG HOLDING AS
FONNES BIL EIENDOM AS
NOK 366,000 rev. · NOK 138,000 profit

FONNES BIL EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FONNES BIL EIENDOM AS

Who owns FONNES BIL EIENDOM AS?

STRANDHAUG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of FONNES BIL EIENDOM AS?

FONNES BIL EIENDOM AS had revenue of NOK 366,000 in 2025.

Where is FONNES BIL EIENDOM AS based?

FONNES BIL EIENDOM AS has its business address in Fonnes.

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.