BIZTRAC BETA
Buying and selling of own real estate

KLEKKENVEIEN 164 AS

Org. no. 828351982 Limited company (AS) Ringerike Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 277,000
Operating profit NOK 186,000
Equity NOK 103,000
Incorporated 2021
Share capital NOK 30,000

KLEKKENVEIEN 164 AS is registered as a limited company in Ringerike, Buskerud with organisation number 828351982. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp av eiendom for utvikling, salg og utleie, deltakelse i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 277,000 in revenue and NOK 186,000 in operating profit.

Key figures · 2025

Revenue
NOK 277,000
Operating profit
NOK 186,000
Equity
NOK 103,000
Est. value
NOK 388,000

Financial health · 2025

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

Who owns KLEKKENVEIEN 164 AS?

VIRAFFEN AS
KLEKKENVEIEN 164 AS
NOK 277,000 rev. · NOK 186,000 profit

KLEKKENVEIEN 164 AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLEKKENVEIEN 164 AS

Who owns KLEKKENVEIEN 164 AS?

VIRAFFEN AS is the largest registered owner, with 40.0%.

What is the revenue of KLEKKENVEIEN 164 AS?

KLEKKENVEIEN 164 AS had revenue of NOK 277,000 in 2025.

Who is the general manager of KLEKKENVEIEN 164 AS?

Sindre Myrlund is registered as general manager of KLEKKENVEIEN 164 AS.

Where is KLEKKENVEIEN 164 AS based?

KLEKKENVEIEN 164 AS has its business address in Hønefoss.

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.