BIZTRAC BETA
COMPANY REGISTER PROFILE
819486352 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

KONGEVEGEN HYTTETOMTER AS

Org. no. 819486352 Limited company (AS) Lærdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 171,000
Operating profit NOK 89,000
Equity NOK 496,000
Incorporated 2017
Share capital NOK 100,000

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 2025 financial year, show NOK 171,000 in revenue and NOK 89,000 in operating profit.

Key figures · 2025

Revenue
NOK 171,000
▲ +2516 %
Operating profit
NOK 89,000
▲ +746 %
Equity
NOK 496,000
▲ +20 %
Est. value
NOK 539,000

Financial health · 2025

Liquidity
2.88
Very good
Current assets ÷ current liabilities
Profitability
12.5%
Good
Return on total assets
Solidity
65.3%
Very good
Equity as a share of total capital

Who owns KONGEVEGEN HYTTETOMTER AS?

KONGEVEGEN HYTTETOMTER AS
NOK 171,000 rev. · NOK 89,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 171,000 in 2025.

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

Report a problem

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