biztrac. BETA
COMPANY REGISTER PROFILE
999328520 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

KINNVEGEN EIENDOM AS

Org. no. 999328520 Limited company (AS) Kinn Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 143,000
Operating profit NOK −263,000
Equity NOK 1.5m
Incorporated 2012
Share capital NOK 6.4m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−263k kr).

KINNVEGEN EIENDOM AS is registered as a limited company in Kinn, Vestland with organisation number 999328520. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 6.4m, divided into 21000 shares. The company's stated purpose is: “Kjøp og slag av eiendom og utvikling av eiendom for salg, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 143,000 in revenue and NOK −263,000 in operating profit.

Key figures · 2025

Revenue
NOK 143,000
▲ +11175 %
Operating profit
NOK −263,000
▲ +18 %
Equity
NOK 1.5m
▼ −53 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
2.39
Very good
Current assets ÷ current liabilities
Profitability
-1.1%
Not satisfactory
Return on total assets
Solidity
6.4%
Weak
Equity as a share of total capital

Who owns KINNVEGEN EIENDOM AS?

KINNVEGEN EIENDOM AS
NOK 143,000 rev. · NOK −263,000 profit

KINNVEGEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KINNVEGEN EIENDOM AS

Who owns KINNVEGEN EIENDOM AS?

ALLBYGG FLORØ INVEST AS is the largest registered owner, with 54.5%.

What is the revenue of KINNVEGEN EIENDOM AS?

KINNVEGEN EIENDOM AS had revenue of NOK 143,000 in 2025.

Where is KINNVEGEN EIENDOM AS based?

KINNVEGEN EIENDOM AS has its business address in Florø.

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.