biztrac. BETA
COMPANY REGISTER PROFILE
930835420 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

RØYSEVEIEN 189 AS

Org. no. 930835420 Limited company (AS) Hole Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 660,000
Operating profit NOK 295,000
Equity NOK 1.5m
Incorporated 2023
Share capital NOK 60,000

RØYSEVEIEN 189 AS is registered as a limited company in Hole, Buskerud with organisation number 930835420. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom og deltakelse i andre virksomheter ved aksjeinnskudd eller på annen måte”. The most recent filed accounts, for the 2025 financial year, show NOK 660,000 in revenue and NOK 295,000 in operating profit.

Key figures · 2025

Revenue
NOK 660,000
▲ +9 %
Operating profit
NOK 295,000
▼ −24 %
Equity
NOK 1.5m
▲ +3 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
40.38
Very good
Current assets ÷ current liabilities
Profitability
9.8%
Satisfactory
Return on total assets
Solidity
41.5%
Very good
Equity as a share of total capital

Who owns RØYSEVEIEN 189 AS?

RØYSEVEIEN 189 AS
NOK 660,000 rev. · NOK 295,000 profit

RØYSEVEIEN 189 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØYSEVEIEN 189 AS

Who owns RØYSEVEIEN 189 AS?

HARATRØEN AS is the largest registered owner, with 50.0%.

What is the revenue of RØYSEVEIEN 189 AS?

RØYSEVEIEN 189 AS had revenue of NOK 660,000 in 2025.

Who is the general manager of RØYSEVEIEN 189 AS?

Kjell Jarle Lad is registered as general manager of RØYSEVEIEN 189 AS.

Where is RØYSEVEIEN 189 AS based?

RØYSEVEIEN 189 AS has its business address in Røyse.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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