BIZTRAC BETA
Construction of residential and non-residential buildings

M2K BYGGTJENESTER AS

Org. no. 935435617 Limited company (AS) Aurskog-Høland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 999,000
Equity NOK 810,000
Incorporated 2025
Employees 11
Share capital NOK 30,000

M2K BYGGTJENESTER AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 935435617. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring/vedlikehold av bygg, kjøp/salg av eiendom, utleie av eiendom og alt som naturlig faller herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 999,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 999,000
Equity
NOK 810,000
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.3%
Good
Equity as a share of total capital

Who owns M2K BYGGTJENESTER AS?

MINDAUGAS KERULIS
M2K BYGGTJENESTER AS
NOK 3.7m rev. · NOK 999,000 profit

M2K BYGGTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M2K BYGGTJENESTER AS

Who owns M2K BYGGTJENESTER AS?

MINDAUGAS KERULIS is the largest registered owner, with 100.0%.

What is the revenue of M2K BYGGTJENESTER AS?

M2K BYGGTJENESTER AS had revenue of NOK 3.7m in 2025.

Who is the general manager of M2K BYGGTJENESTER AS?

Mindaugas Kerulis is registered as general manager of M2K BYGGTJENESTER AS.

Where is M2K BYGGTJENESTER AS based?

M2K BYGGTJENESTER AS has its business address in Rømskog.

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.