BIZTRAC BETA
Architectural activities

M3 ARKITEKTER AS

Org. no. 911994585 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 934,000
Operating profit NOK −55,000
Equity NOK −37,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−37k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−55k kr).

M3 ARKITEKTER AS is registered as a limited company in Asker, Akershus with organisation number 911994585. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av arkitekttjenester og alt som naturlig hører med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 934,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 934,000
Operating profit
NOK −55,000
Equity
NOK −37,000

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-14.1%
Weak
Equity as a share of total capital

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

Who owns M3 ARKITEKTER AS?

STELLA HOFFMANN
M3 ARKITEKTER AS
NOK 934,000 rev. · NOK −55,000 profit

M3 ARKITEKTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about M3 ARKITEKTER AS

Who owns M3 ARKITEKTER AS?

STELLA HOFFMANN is the largest registered owner, with 70.0%.

What is the revenue of M3 ARKITEKTER AS?

M3 ARKITEKTER AS had revenue of NOK 934,000 in 2025.

Who is the general manager of M3 ARKITEKTER AS?

Stella Hoffmann is registered as general manager of M3 ARKITEKTER AS.

Where is M3 ARKITEKTER AS based?

M3 ARKITEKTER AS has its business address in Tofte.

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.