BIZTRAC BETA
Other support activities to arts and performing arts

MITECH HOLDING AS

Org. no. 918341773 Limited company (AS) Kristiansand Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 9.1m
Operating profit NOK −1.9m
Equity NOK 7.2m
Incorporated 2016
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,9 mill kr).

MITECH HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 918341773. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2016. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Utleie og salg av sceneteknisk materiell. Reparasjon av musikkutstyr. Investering i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.1m in revenue and NOK −1.9m in operating profit.

Key figures · 2024

Revenue
NOK 9.1m
Operating profit
NOK −1.9m
Equity
NOK 7.2m
Est. value
NOK 16.8m

Financial health · 2024

Liquidity
4.16
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.9%
Good
Equity as a share of total capital

Who owns MITECH HOLDING AS?

MIKE THOMAS MOEN
MITECH HOLDING AS
NOK 9.1m rev. · NOK −1.9m profit

MITECH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MITECH HOLDING AS own?

MITECH HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MITECH HOLDING AS

Who owns MITECH HOLDING AS?

MIKE THOMAS MOEN is the largest registered owner, with 100.0%.

What is the revenue of MITECH HOLDING AS?

MITECH HOLDING AS had revenue of NOK 9.1m in 2024.

Where is MITECH HOLDING AS based?

MITECH HOLDING AS has its business address in Kristiansand S.

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.