BIZTRAC BETA
COMPANY REGISTER PROFILE
922846391 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

ØVERIET OSLO AS

Org. no. 922846391 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 10.9m
Operating profit NOK 726,000
Equity NOK 3.9m
Incorporated 2019
Share capital NOK 60,000

ØVERIET OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 922846391. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Investering, drift og utleie av eiendom, kulturvirksomhet og beslektede områder.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.9m in revenue and NOK 726,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.9m
Operating profit
NOK 726,000
Equity
NOK 3.9m
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.6%
Good
Equity as a share of total capital

Who owns ØVERIET OSLO AS?

19 HERTZ AS
ØVERIET OSLO AS
NOK 10.9m rev. · NOK 726,000 profit

ØVERIET OSLO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ØVERIET OSLO AS er morselskap for 1 datterselskap:

Frequently asked questions about ØVERIET OSLO AS

Who owns ØVERIET OSLO AS?

19 HERTZ AS is the largest registered owner, with 100.0%.

What is the revenue of ØVERIET OSLO AS?

ØVERIET OSLO AS had revenue of NOK 10.9m in 2025.

Who is the general manager of ØVERIET OSLO AS?

Markus Lindstøl Aase is registered as general manager of ØVERIET OSLO AS.

Where is ØVERIET OSLO AS based?

ØVERIET OSLO AS has its business address in Oslo.

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.