BIZTRAC BETA
Uoppgitt

OMMEDAL HOLDING AS

Org. no. 924712406 Limited company (AS) Eidskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −31,000
Equity NOK −11,000
Incorporated 2020
Share capital NOK 150,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−31k kr).

OMMEDAL HOLDING AS is registered as a limited company in Eidskog, Innlandet with organisation number 924712406. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Eie aksjer, samt investeringer i virksomheter av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −31,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −31,000
Equity
NOK −11,000

Financial health · 2024

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

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

Who owns OMMEDAL HOLDING AS?

Mathias Tukun Ommedal
OMMEDAL HOLDING AS
NOK 0 rev. · NOK −31,000 profit

OMMEDAL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OMMEDAL HOLDING AS own?

OMMEDAL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OMMEDAL HOLDING AS

Who owns OMMEDAL HOLDING AS?

Mathias Tukun Ommedal is the largest registered owner, with 100.0%.

What is the revenue of OMMEDAL HOLDING AS?

OMMEDAL HOLDING AS had revenue of NOK 0 in 2024.

Where is OMMEDAL HOLDING AS based?

OMMEDAL HOLDING AS has its business address in Skotterud.

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.