BIZTRAC BETA
Rental and operating of own or leased real estate

OSLOVEIEN AS

Org. no. 925626317 Limited company (AS) Lillestrøm Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 524,000
Operating profit NOK 365,000
Equity NOK 275,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-02 Adresseendring registrert 2026-07-02.

OSLOVEIEN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 925626317. 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 1000 shares. The company's stated purpose is: “Kjøp, utleie og salg av boliger og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 524,000 in revenue and NOK 365,000 in operating profit.

Key figures · 2024

Revenue
NOK 524,000
Operating profit
NOK 365,000
Equity
NOK 275,000
Est. value
NOK 663,000

Financial health · 2024

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

Who owns OSLOVEIEN AS?

FREDENSBORG HOLDING AS
OSLOVEIEN AS
NOK 524,000 rev. · NOK 365,000 profit

OSLOVEIEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSLOVEIEN AS

Who owns OSLOVEIEN AS?

FREDENSBORG HOLDING AS is the largest registered owner, with 35.0%.

What is the revenue of OSLOVEIEN AS?

OSLOVEIEN AS had revenue of NOK 524,000 in 2024.

Who is the general manager of OSLOVEIEN AS?

Åge Haakonsen is registered as general manager of OSLOVEIEN AS.

Where is OSLOVEIEN AS based?

OSLOVEIEN AS has its business address in Lillestrøm.

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.