BIZTRAC BETA
Rental and operating of own or leased real estate

ASKVEIEN 6 HØNEFOSS AS

Org. no. 929182340 Limited company (AS) Ringerike Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 798,000
Operating profit NOK 93,000
Equity NOK 6.4m
Incorporated 2022
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASKVEIEN 6 HØNEFOSS AS is registered as a limited company in Ringerike, Buskerud with organisation number 929182340. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, drift og utvikling av fast eiendom, herunder delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 798,000 in revenue and NOK 93,000 in operating profit.

Key figures · 2024

Revenue
NOK 798,000
Operating profit
NOK 93,000
Equity
NOK 6.4m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns ASKVEIEN 6 HØNEFOSS AS?

ASLAKSRUD HOLDING AS
ASKVEIEN 6 HØNEFOSS AS
NOK 798,000 rev. · NOK 93,000 profit

ASKVEIEN 6 HØNEFOSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASKVEIEN 6 HØNEFOSS AS

Who owns ASKVEIEN 6 HØNEFOSS AS?

ASLAKSRUD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ASKVEIEN 6 HØNEFOSS AS?

ASKVEIEN 6 HØNEFOSS AS had revenue of NOK 798,000 in 2024.

Where is ASKVEIEN 6 HØNEFOSS AS based?

ASKVEIEN 6 HØNEFOSS 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.