BIZTRAC BETA
Rental and operating of own or leased real estate

OLEG EIENDOM AS

Org. no. 914919479 Limited company (AS) Trondheim Incorporated 1958 Active
Ownership graph ↗
Revenue 2025 NOK 655,000
Operating profit NOK 433,000
Equity NOK 2.2m
Incorporated 1958
Share capital NOK 100,000

Signals

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

OLEG EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914919479. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1958. Registered share capital is NOK 100,000. The company's stated purpose is: “Erverv, planlegging og prosjektering, utbygging, drift og utleie av eiendom og bygg. Videre har selskapet til formål å organisere eller delta i tiltak eller selskap som har sammenheng med ovennevnte formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 655,000 in revenue and NOK 433,000 in operating profit.

Key figures · 2025

Revenue
NOK 655,000
Operating profit
NOK 433,000
Equity
NOK 2.2m
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.9%
Very good
Equity as a share of total capital

Who owns OLEG EIENDOM AS?

SUNDVALL EIENDOM AS
OLEG EIENDOM AS
NOK 655,000 rev. · NOK 433,000 profit

OLEG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLEG EIENDOM AS

Who owns OLEG EIENDOM AS?

SUNDVALL EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of OLEG EIENDOM AS?

OLEG EIENDOM AS had revenue of NOK 655,000 in 2025.

Where is OLEG EIENDOM AS based?

OLEG EIENDOM AS has its business address in Trondheim.

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.