BIZTRAC BETA
Industrial product and fashion design activities

M CODE AS

Org. no. 922328943 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 900,000
Operating profit NOK 10,000
Equity NOK 1.7m
Incorporated 2019
Share capital NOK 68,000

M CODE AS is registered as a limited company in Oslo, Oslo with organisation number 922328943. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2019. Registered share capital is NOK 68,000, divided into 67500 shares. The company's stated purpose is: “Konsulentvirksomhet og investering innenfor den kreative bransje, tekstil, interiør og tilbehør, design og produksjon og annen aktivitet med naturlig tilhørighet innen dette feltet.”. The most recent filed accounts, for the 2025 financial year, show NOK 900,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2025

Revenue
NOK 900,000
Operating profit
NOK 10,000
Equity
NOK 1.7m
Est. value
NOK 870,000

Financial health · 2024

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

Who owns M CODE AS?

MARIT ROTNES ANGELFOSS
M CODE AS
NOK 900,000 rev. · NOK 10,000 profit

M CODE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M CODE AS own?

M CODE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about M CODE AS

Who owns M CODE AS?

MARIT ROTNES ANGELFOSS is the largest registered owner, with 100.0%.

What is the revenue of M CODE AS?

M CODE AS had revenue of NOK 900,000 in 2025.

Who is the general manager of M CODE AS?

Marit Rotnes Angelfoss is registered as general manager of M CODE AS.

Where is M CODE AS based?

M CODE 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.