BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

MK TAKST AS

Org. no. 929065441 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 295,000
Operating profit NOK 134,000
Equity NOK −55,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−55k kr).

MK TAKST AS is registered as a limited company in Bærum, Akershus with organisation number 929065441. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilstandsrapport, verditaksering og skadetakst av bolig.”. The most recent filed accounts, for the 2025 financial year, show NOK 295,000 in revenue and NOK 134,000 in operating profit.

Key figures · 2025

Revenue
NOK 295,000
Operating profit
NOK 134,000
Equity
NOK −55,000
Est. value
NOK 608,000

Financial health · 2025

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

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

Who owns MK TAKST AS?

MORTEN KJØNNIKSEN
MK TAKST AS
NOK 295,000 rev. · NOK 134,000 profit

MK TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MK TAKST AS

Who owns MK TAKST AS?

MORTEN KJØNNIKSEN is the largest registered owner, with 100.0%.

What is the revenue of MK TAKST AS?

MK TAKST AS had revenue of NOK 295,000 in 2025.

Who is the general manager of MK TAKST AS?

Morten Kjønniksen is registered as general manager of MK TAKST AS.

Where is MK TAKST AS based?

MK TAKST AS has its business address in Blommenholm.

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.