BIZTRAC BETA
Accounting and bookkeeping

OMBE ACCOUNTING AS

Org. no. 924379693 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 23,000
Equity NOK 60,000
Incorporated 2019
Share capital NOK 30,000

OMBE ACCOUNTING AS is registered as a limited company in Drammen, Buskerud with organisation number 924379693. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Regnskapsføring samt konsulenttjenester innen administrativ og organisasjonsteknisk tjenesteyting samt ved kjøp av aksjer eller på annen måte å delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 23,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 23,000
Equity
NOK 60,000
Est. value
NOK 155,000

Financial health · 2025

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

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

Who owns OMBE ACCOUNTING AS?

SKAHAM INVEST AS
OMBE ACCOUNTING AS
NOK 1.4m rev. · NOK 23,000 profit

OMBE ACCOUNTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OMBE ACCOUNTING AS

Who owns OMBE ACCOUNTING AS?

SKAHAM INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of OMBE ACCOUNTING AS?

OMBE ACCOUNTING AS had revenue of NOK 1.4m in 2025.

Who is the general manager of OMBE ACCOUNTING AS?

Ole Hallvard Haugen is registered as general manager of OMBE ACCOUNTING AS.

Where is OMBE ACCOUNTING AS based?

OMBE ACCOUNTING AS has its business address in Drammen.

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.