BIZTRAC BETA
Other real estate activities on a fee or contract basis

M2 STING AS

Org. no. 918265910 Limited company (AS) Bodø Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 959,000
Equity NOK 1.4m
Incorporated 2016
Share capital NOK 30,000

M2 STING AS is registered as a limited company in Bodø, Nordland with organisation number 918265910. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapets formål er å levere tjenester innen taksering av eiendommer og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 959,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 959,000
Equity
NOK 1.4m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns M2 STING AS?

STÅLE LIMSTRAND
M2 STING AS
NOK 1.2m rev. · NOK 959,000 profit

M2 STING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M2 STING AS own?

M2 STING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about M2 STING AS

Who owns M2 STING AS?

STÅLE LIMSTRAND is the largest registered owner, with 100.0%.

What is the revenue of M2 STING AS?

M2 STING AS had revenue of NOK 1.2m in 2024.

Where is M2 STING AS based?

M2 STING AS has its business address in Bodø.

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.