BIZTRAC BETA
Rental and operating of own or leased real estate

HØGÅSVEIEN 3 AS

Org. no. 925782769 Limited company (AS) Ringerike Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 457,000
Operating profit NOK 291,000
Equity NOK 35,000
Incorporated 2020
Share capital NOK 30,000

HØGÅSVEIEN 3 AS is registered as a limited company in Ringerike, Buskerud with organisation number 925782769. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1200 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 457,000 in revenue and NOK 291,000 in operating profit.

Key figures · 2025

Revenue
NOK 457,000
Operating profit
NOK 291,000
Equity
NOK 35,000
Est. value
NOK 355,000

Financial health · 2025

Liquidity
-0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

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

Who owns HØGÅSVEIEN 3 AS?

WENCHE ØKSNES FJELDAVLI
HØGÅSVEIEN 3 AS
NOK 457,000 rev. · NOK 291,000 profit

HØGÅSVEIEN 3 AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HØGÅSVEIEN 3 AS own?

HØGÅSVEIEN 3 AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

HØGÅSVEIEN 3 AS er morselskap for 2 datterselskaper:

Frequently asked questions about HØGÅSVEIEN 3 AS

Who owns HØGÅSVEIEN 3 AS?

WENCHE ØKSNES FJELDAVLI is the largest registered owner, with 25.0%.

What is the revenue of HØGÅSVEIEN 3 AS?

HØGÅSVEIEN 3 AS had revenue of NOK 457,000 in 2025.

Where is HØGÅSVEIEN 3 AS based?

HØGÅSVEIEN 3 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.