BIZTRAC BETA
Business and other management consultancy activities

MØNSTR AS

Org. no. 928468070 Limited company (AS) Oppdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −102,000
Equity NOK 163,000
Incorporated 2021
Share capital NOK 100,000

Signals

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

MØNSTR AS is registered as a limited company in Oppdal, Trøndelag with organisation number 928468070. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 1500 shares. The company's stated purpose is: “Å skaffe til veie kapital for investeringer i aksjer og andeler i andre selskaper innenfor enhver bransje selskapet måtte finne det hensiktsmessig å investere i.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −102,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −102,000
Equity
NOK 163,000
Est. value
NOK 266,000

Financial health · 2024

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.7%
Not satisfactory
Equity as a share of total capital

Who owns MØNSTR AS?

TIENTI AS
MØNSTR AS
NOK 0 rev. · NOK −102,000 profit

MØNSTR AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MØNSTR AS own?

MØNSTR AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

MØNSTR AS er morselskap for 1 datterselskap:

Frequently asked questions about MØNSTR AS

Who owns MØNSTR AS?

TIENTI AS is the largest registered owner, with 33.3%.

What is the revenue of MØNSTR AS?

MØNSTR AS had revenue of NOK 0 in 2024.

Where is MØNSTR AS based?

MØNSTR AS has its business address in Oppdal.

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.