BIZTRAC BETA
Plumbing installation

KONGSVEGEN 64 AS

Org. no. 998727685 Limited company (AS) Nord-Aurdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 72,000
Operating profit NOK −78,000
Equity NOK 53,000
Incorporated 2012
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−78k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KONGSVEGEN 64 AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 998727685. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive med kjøp, salg og utleie av fast eiendom og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 72,000 in revenue and NOK −78,000 in operating profit.

Key figures · 2024

Revenue
NOK 72,000
Operating profit
NOK −78,000
Equity
NOK 53,000
Est. value
NOK 48,000

Financial health · 2024

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

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

Who owns KONGSVEGEN 64 AS?

OLSEN EIENDOM AS
KONGSVEGEN 64 AS
NOK 72,000 rev. · NOK −78,000 profit

KONGSVEGEN 64 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSVEGEN 64 AS

Who owns KONGSVEGEN 64 AS?

OLSEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KONGSVEGEN 64 AS?

KONGSVEGEN 64 AS had revenue of NOK 72,000 in 2024.

Where is KONGSVEGEN 64 AS based?

KONGSVEGEN 64 AS has its business address in Leira I Valdres.

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.