BIZTRAC BETA
Other captive investment companies

MESCO AS

Org. no. 980165493 Limited company (AS) Kragerø Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK −293,000
Operating profit NOK −339,000
Equity NOK 41.3m
Incorporated 1998
Share capital NOK 147,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−339k kr).

MESCO AS is registered as a limited company in Kragerø, Telemark with organisation number 980165493. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1998. Registered share capital is NOK 147,000, divided into 49131 shares. The company's stated purpose is: “Investeringer i verdipapirer, fast eiendom med videre samt alt som står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK −293,000 in revenue and NOK −339,000 in operating profit.

Key figures · 2024

Revenue
NOK −293,000
Operating profit
NOK −339,000
Equity
NOK 41.3m
Est. value
NOK 28.6m

Financial health · 2024

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

Who owns MESCO AS?

MONS EINAR STANGE
MESCO AS
NOK −293,000 rev. · NOK −339,000 profit

MESCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MESCO AS own?

MESCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MESCO AS

Who owns MESCO AS?

MONS EINAR STANGE is the largest registered owner, with 100.0%.

What is the revenue of MESCO AS?

MESCO AS had revenue of NOK −293,000 in 2024.

Who is the general manager of MESCO AS?

Mons Einar Stange is registered as general manager of MESCO AS.

Where is MESCO AS based?

MESCO AS has its business address in Kragerø.

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.