BIZTRAC BETA
Repair and maintenance of motor vehicles

KMS BILELEKTRONIKK AS

Org. no. 912838412 Limited company (AS) Steinkjer Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 85,000
Equity NOK 228,000
Incorporated 2013
Share capital NOK 30,000

KMS BILELEKTRONIKK AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 912838412. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bilreparasjoner og reparasjon av bilelektronikk, kjøp og salg av bildeler, renholdstjenester samt annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 85,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 85,000
Equity
NOK 228,000
Est. value
NOK 465,000

Financial health · 2025

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

Who owns KMS BILELEKTRONIKK AS?

MICHAL LUDWIK SKRZYNIARZ
KMS BILELEKTRONIKK AS
NOK 1.6m rev. · NOK 85,000 profit

KMS BILELEKTRONIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KMS BILELEKTRONIKK AS

Who owns KMS BILELEKTRONIKK AS?

MICHAL LUDWIK SKRZYNIARZ is the largest registered owner, with 50.0%.

What is the revenue of KMS BILELEKTRONIKK AS?

KMS BILELEKTRONIKK AS had revenue of NOK 1.6m in 2025.

Who is the general manager of KMS BILELEKTRONIKK AS?

Katarzyna Lilianna Skrzyniarz is registered as general manager of KMS BILELEKTRONIKK AS.

Where is KMS BILELEKTRONIKK AS based?

KMS BILELEKTRONIKK AS has its business address in Beitstad.

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.