BIZTRAC BETA
COMPANY REGISTER PROFILE
921045255 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

ODOACER AS

Org. no. 921045255 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2018
Share capital NOK 30,000

ODOACER AS is registered as a limited company in Oslo, Oslo with organisation number 921045255. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 4240 shares. The company's stated purpose is: “Investere i ulike selskaper, samt eie andre realaktiva.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ODOACER AS?

ODOACER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ODOACER AS own?

ODOACER AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about ODOACER AS

Who owns ODOACER AS?

CHRISTIAN PEDER SLETNER HUNDEVADT is the largest registered owner, with 100.0%.

Where is ODOACER AS based?

ODOACER AS has its business address in Oslo.

Property

Business address c/o Christian Hundevadt Olaf Bulls vei 46, 0765 Oslo
Cadastral unit 301-33/2168/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 22 units

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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