BIZTRAC BETA
Technical testing and analysis

KRANKONTROLLEN AS

Org. no. 966636718 Limited company (AS) Lillestrøm Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 15.6m
Operating profit NOK 1.8m
Equity NOK 6.8m
Incorporated 1993
Employees 12
Share capital NOK 250,000

KRANKONTROLLEN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 966636718. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 1993 and has 12 registered employees. Registered share capital is NOK 250,000, divided into 100 shares. The company's stated purpose is: “Kontroll, sertifisering, service, salg, opplæring og rådgivende konsulenttjenester innenfor løfte- og transportteknisk område, samt annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.6m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 15.6m
Operating profit
NOK 1.8m
Equity
NOK 6.8m
Est. value
NOK 13.2m

Financial health · 2025

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

Who owns KRANKONTROLLEN AS?

LEON GILINSKY
KRANKONTROLLEN AS
NOK 15.6m rev. · NOK 1.8m profit

KRANKONTROLLEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRANKONTROLLEN AS

Who owns KRANKONTROLLEN AS?

LEON GILINSKY is the largest registered owner, with 60.0%.

What is the revenue of KRANKONTROLLEN AS?

KRANKONTROLLEN AS had revenue of NOK 15.6m in 2025.

Who is the general manager of KRANKONTROLLEN AS?

Raymond Gilinsky is registered as general manager of KRANKONTROLLEN AS.

Where is KRANKONTROLLEN AS based?

KRANKONTROLLEN AS has its business address in Lillestrøm.

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.