BIZTRAC BETA
Development of building projects

KONGEVEGEN HYTTETOMTER AS

Org. no. 819486352 Limited company (AS) Lærdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7,000
Operating profit NOK −14,000
Equity NOK 414,000
Incorporated 2017
Share capital NOK 100,000

Signals

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

KONGEVEGEN HYTTETOMTER AS is registered as a limited company in Lærdal, Vestland with organisation number 819486352. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Opparbeide og utvikle hyttetomter for salg, samt opparbeide nødvendig infrastruktur. Drifte infrastruktur og andre tenester som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 7,000
Operating profit
NOK −14,000
Equity
NOK 414,000
Est. value
NOK 293,000

Financial health · 2024

Liquidity
2.71
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
63.1%
Very good
Equity as a share of total capital

Who owns KONGEVEGEN HYTTETOMTER AS?

KNUT HORVATH MARISTUEN
KONGEVEGEN HYTTETOMTER AS
NOK 7,000 rev. · NOK −14,000 profit

KONGEVEGEN HYTTETOMTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGEVEGEN HYTTETOMTER AS

Who owns KONGEVEGEN HYTTETOMTER AS?

KNUT HORVATH MARISTUEN is the largest registered owner, with 100.0%.

What is the revenue of KONGEVEGEN HYTTETOMTER AS?

KONGEVEGEN HYTTETOMTER AS had revenue of NOK 7,000 in 2024.

Where is KONGEVEGEN HYTTETOMTER AS based?

KONGEVEGEN HYTTETOMTER AS has its business address in Borgund.

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.