biztrac. BETA
COMPANY REGISTER PROFILE
920380239 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Processing of tea and coffee

MIT HOLDING AS

Org. no. 920380239 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −56,000
Equity NOK 1.3m
Incorporated 2018
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−56k kr).

MIT HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920380239. The business is classified under processing of tea and coffee (NACE 10.830). The company was incorporated in 2018. Registered share capital is NOK 1.2m, divided into 1200 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −56,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −56,000
▼ −37 %
Equity
NOK 1.3m
▼ −1 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
5.75
Very good
Current assets ÷ current liabilities
Profitability
-1.3%
Not satisfactory
Return on total assets
Solidity
99.1%
Very good
Equity as a share of total capital

Who owns MIT HOLDING AS?

MIT HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MIT HOLDING AS own?

MIT HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MIT HOLDING AS

Who owns MIT HOLDING AS?

Tor Schjølberg is the largest registered owner, with 25.0%.

What is the revenue of MIT HOLDING AS?

MIT HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of MIT HOLDING AS?

Idar André Ellingsen is registered as general manager of MIT HOLDING AS.

Where is MIT HOLDING AS based?

MIT HOLDING AS has its business address in Jonsvatnet.

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.