BIZTRAC BETA
Rental and operating of own or leased real estate

OSLOVEIEN 23 AS

Org. no. 953965682 Limited company (AS) Ringerike Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 1.2m
Equity NOK 3.3m
Incorporated 1989
Share capital NOK 300,000

Signals

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

OSLOVEIEN 23 AS is registered as a limited company in Ringerike, Buskerud with organisation number 953965682. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 300,000, divided into 800 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 1.2m
Equity
NOK 3.3m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns OSLOVEIEN 23 AS?

XPND AS
OSLOVEIEN 23 AS
NOK 1.6m rev. · NOK 1.2m profit

OSLOVEIEN 23 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLOVEIEN 23 AS

Who owns OSLOVEIEN 23 AS?

XPND AS is the largest registered owner, with 100.0%.

What is the revenue of OSLOVEIEN 23 AS?

OSLOVEIEN 23 AS had revenue of NOK 1.6m in 2025.

Who is the general manager of OSLOVEIEN 23 AS?

Morten Pettersen is registered as general manager of OSLOVEIEN 23 AS.

Where is OSLOVEIEN 23 AS based?

OSLOVEIEN 23 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.