biztrac. BETA
COMPANY REGISTER PROFILE
915416969 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Electrical installation

OMB INVEST AS

Org. no. 915416969 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 105
Equity NOK −35,000
Incorporated 2015
Share capital NOK 65,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−35k kr).

OMB INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 915416969. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2015. Registered share capital is NOK 65,000, divided into 100 shares. The company's stated purpose is: “Investering i og deltagelse i andre selskaper gjennom aksjebesittelse eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 105 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 105
▲ +105 %
Equity
NOK −35,000
▲ +1 %
Est. value
NOK 617

Financial health · 2025

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
0.1%
Not satisfactory
Return on total assets
Solidity
-13.6%
Weak
Equity as a share of total capital

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

Who owns OMB INVEST AS?

OMB INVEST AS
NOK 0 rev. · NOK 105 profit

OMB INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OMB INVEST AS own?

OMB INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OMB INVEST AS

Who owns OMB INVEST AS?

Ole Marius Bakke is the largest registered owner, with 100.0%.

What is the revenue of OMB INVEST AS?

OMB INVEST AS had revenue of NOK 0 in 2025.

Where is OMB INVEST AS based?

OMB INVEST 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 03.10.2026.

Report a problem

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