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

M2 TAKSERING AS

Org. no. 911548860 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 835,000
Operating profit NOK 486,000
Equity NOK 2.0m
Incorporated 2013
Share capital NOK 30,000

M2 TAKSERING AS is registered as a limited company in Bærum, Akershus with organisation number 911548860. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Taksering av næring- og boligbygg samt taksering av skader og opptre som skjønnsmann.”. The most recent filed accounts, for the 2024 financial year, show NOK 835,000 in revenue and NOK 486,000 in operating profit.

Key figures · 2024

Revenue
NOK 835,000
Operating profit
NOK 486,000
Equity
NOK 2.0m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns M2 TAKSERING AS?

FRANK-ROE VASSENG
M2 TAKSERING AS
NOK 835,000 rev. · NOK 486,000 profit

M2 TAKSERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M2 TAKSERING AS own?

M2 TAKSERING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about M2 TAKSERING AS

Who owns M2 TAKSERING AS?

FRANK-ROE VASSENG is the largest registered owner, with 100.0%.

What is the revenue of M2 TAKSERING AS?

M2 TAKSERING AS had revenue of NOK 835,000 in 2024.

Who is the general manager of M2 TAKSERING AS?

Frank-Roe Vasseng is registered as general manager of M2 TAKSERING AS.

Where is M2 TAKSERING AS based?

M2 TAKSERING AS has its business address in Snarøya.

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.