BIZTRAC BETA
Activities of excursion and event organisers

NEW START MCT AS

Org. no. 833725572 Limited company (AS) Nesodden Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 20,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

NEW START MCT AS is registered as a limited company in Nesodden, Akershus with organisation number 833725572. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Organisering av kunstutstillinger, festivaler, konserter og andre kunst- og underholdningsarr.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 20,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns NEW START MCT AS?

THS EIENDOM AS
NEW START MCT AS
NOK 0 rev. · NOK −9,000 profit

NEW START MCT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEW START MCT AS

Who owns NEW START MCT AS?

THS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of NEW START MCT AS?

NEW START MCT AS had revenue of NOK 0 in 2025.

Who is the general manager of NEW START MCT AS?

Thomas Sletten is registered as general manager of NEW START MCT AS.

Where is NEW START MCT AS based?

NEW START MCT AS has its business address in Bjørnemyr.

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.