BIZTRAC BETA
Joinery installation

MAX TEKNIKK AS

Org. no. 923207066 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 431,000
Operating profit NOK −33,000
Equity NOK 61,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−33k kr).

MAX TEKNIKK AS is registered as a limited company in Asker, Akershus with organisation number 923207066. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Renovasjon og montering av møbler, diverse oppussingstjenester, billakkering, samt andre tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 431,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2024

Revenue
NOK 431,000
Operating profit
NOK −33,000
Equity
NOK 61,000
Est. value
NOK 176,000

Financial health · 2024

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

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

Who owns MAX TEKNIKK AS?

JAROSLAW MULARSKI
MAX TEKNIKK AS
NOK 431,000 rev. · NOK −33,000 profit

MAX TEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAX TEKNIKK AS

Who owns MAX TEKNIKK AS?

JAROSLAW MULARSKI is the largest registered owner, with 100.0%.

What is the revenue of MAX TEKNIKK AS?

MAX TEKNIKK AS had revenue of NOK 431,000 in 2024.

Who is the general manager of MAX TEKNIKK AS?

Karol Mularski is registered as general manager of MAX TEKNIKK AS.

Where is MAX TEKNIKK AS based?

MAX TEKNIKK AS has its business address in Hyggen.

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.