BIZTRAC BETA
Research and experimental development on natural sciences and engineering

MASMASMAS AS

Org. no. 933099148 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 24,000
Incorporated 2023
Share capital NOK 33,000

Signals

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

MASMASMAS AS is registered as a limited company in Oslo, Oslo with organisation number 933099148. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2023. Registered share capital is NOK 33,000, divided into 330 shares. The company's stated purpose is: “Å drive investeringer og alt som står i forbindelse med dette, herunder å eie aksjer og andeler i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 24,000
Est. value
NOK 39,000

Financial health · 2025

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.5%
Weak
Equity as a share of total capital

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

Who owns MASMASMAS AS?

BOT AS
MASMASMAS AS
NOK 0 rev. · NOK −24,000 profit

MASMASMAS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MASMASMAS AS own?

MASMASMAS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MASMASMAS AS

Who owns MASMASMAS AS?

BOT AS is the largest registered owner, with 40.0%.

What is the revenue of MASMASMAS AS?

MASMASMAS AS had revenue of NOK 0 in 2025.

Where is MASMASMAS AS based?

MASMASMAS AS has its business address in Oslo.

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.