BIZTRAC BETA
Accounting and bookkeeping

MISTEL ACCOUNTING AS

Org. no. 821641802 Limited company (AS) Horten Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 307,000
Equity NOK 1.2m
Incorporated 2018
Share capital NOK 500,000

MISTEL ACCOUNTING AS is registered as a limited company in Horten, Vestfold with organisation number 821641802. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Regnskapsførsel og konsulentarbeid samt virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 307,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 307,000
Equity
NOK 1.2m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns MISTEL ACCOUNTING AS?

JMC AS
MISTEL ACCOUNTING AS
NOK 2.4m rev. · NOK 307,000 profit

MISTEL ACCOUNTING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MISTEL ACCOUNTING AS own?

MISTEL ACCOUNTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MISTEL ACCOUNTING AS

Who owns MISTEL ACCOUNTING AS?

JMC AS is the largest registered owner, with 35.0%.

What is the revenue of MISTEL ACCOUNTING AS?

MISTEL ACCOUNTING AS had revenue of NOK 2.4m in 2025.

Who is the general manager of MISTEL ACCOUNTING AS?

Kasper Østergaard Wessel is registered as general manager of MISTEL ACCOUNTING AS.

Where is MISTEL ACCOUNTING AS based?

MISTEL ACCOUNTING AS has its business address in Horten.

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.