biztrac. BETA
COMPANY REGISTER PROFILE
929229584 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠M3 ARMERING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Specialised construction activities in civil engineering

M3 ARMERING AS

Org. no. 929229584 Limited company (AS) Asker Incorporated 2022 In liquidation
Revenue 2025 NOK 20.6m
Operating profit NOK 740,000
Equity NOK 4.7m
Incorporated 2022
Employees 6
Share capital NOK 100,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

M3 ARMERING AS is registered as a limited company in Asker, Akershus with organisation number 929229584. The business is classified under specialised construction activities in civil engineering (NACE 43.500). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utførende i armeringsarbeider, forskalingsarbeider og betongstøp samt andre tjenester naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.6m in revenue and NOK 740,000 in operating profit.

Key figures · 2025

Revenue
NOK 20.6m
▲ +1 %
Operating profit
NOK 740,000
▼ −82 %
Equity
NOK 4.7m
▲ +4 %

Financial health · 2025

Liquidity
2.13
Very good
Current assets ÷ current liabilities
Profitability
7.6%
Satisfactory
Return on total assets
Solidity
53.6%
Very good
Equity as a share of total capital

Who owns M3 ARMERING AS?

M3 ARMERING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about M3 ARMERING AS

Who owns M3 ARMERING AS?

TITTAN INVEST AS is the largest registered owner, with 25.0%.

What is the revenue of M3 ARMERING AS?

M3 ARMERING AS had revenue of NOK 20.6m in 2025.

Where is M3 ARMERING AS based?

M3 ARMERING AS has its business address in Asker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.