BIZTRAC BETA
Retail sale of motor vehicles

MK BILTEKNIKK AS

Org. no. 924782625 Limited company (AS) Sarpsborg Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 669,000
Operating profit NOK −433,000
Equity NOK 3,000
Incorporated 2020
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−433k kr).

MK BILTEKNIKK AS is registered as a limited company in Sarpsborg, Østfold with organisation number 924782625. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2020. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Import og eksport av biler og bildeler, kjøp og salg av bruktbiler og bildeler. Rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 669,000 in revenue and NOK −433,000 in operating profit.

Key figures · 2025

Revenue
NOK 669,000
Operating profit
NOK −433,000
Equity
NOK 3,000
Est. value
NOK 219,000

Financial health · 2025

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

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

Who owns MK BILTEKNIKK AS?

PRZEMYSLAW MILEWSKI
MK BILTEKNIKK AS
NOK 669,000 rev. · NOK −433,000 profit

MK BILTEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MK BILTEKNIKK AS

Who owns MK BILTEKNIKK AS?

PRZEMYSLAW MILEWSKI is the largest registered owner, with 50.0%.

What is the revenue of MK BILTEKNIKK AS?

MK BILTEKNIKK AS had revenue of NOK 669,000 in 2025.

Who is the general manager of MK BILTEKNIKK AS?

Michal Kolakowski is registered as general manager of MK BILTEKNIKK AS.

Where is MK BILTEKNIKK AS based?

MK BILTEKNIKK AS has its business address in Klavestadhaugen.

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.