BIZTRAC BETA
Other construction installation

KONE AKSJESELSKAP

Org. no. 918201548 Limited company (AS) Oslo Incorporated 1973 Active
Ownership graph ↗
Revenue 2024 NOK 886.3m
Operating profit NOK 40.3m
Equity NOK 57.2m
Incorporated 1973
Employees 351
Share capital NOK 8.1m

KONE AKSJESELSKAP is registered as a limited company in Oslo, Oslo with organisation number 918201548. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 1973 and has 351 registered employees. Registered share capital is NOK 8.1m. The company's stated purpose is: “Industri og verkstedvirksomhet, agentur og handel, samt dermed i forbindelse stående virksomhet, her- under deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 886.3m in revenue and NOK 40.3m in operating profit.

Key figures · 2024

Revenue
NOK 886.3m
Operating profit
NOK 40.3m
Equity
NOK 57.2m
Est. value
NOK 160.2m

Financial health · 2024

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.4%
Satisfactory
Equity as a share of total capital

Who owns KONE AKSJESELSKAP?

KONE CORPORATION
KONE AKSJESELSKAP
NOK 886.3m rev. · NOK 40.3m profit

KONE AKSJESELSKAP has 1 registered shareholder:

All shareholders and roles →

Group structure

KONE AKSJESELSKAP er morselskap for 1 datterselskap:

Frequently asked questions about KONE AKSJESELSKAP

Who owns KONE AKSJESELSKAP?

KONE CORPORATION is the largest registered owner, with 100.0%.

What is the revenue of KONE AKSJESELSKAP?

KONE AKSJESELSKAP had revenue of NOK 886.3m in 2024.

Who is the general manager of KONE AKSJESELSKAP?

Richard Robert Antero Huber is registered as general manager of KONE AKSJESELSKAP.

Where is KONE AKSJESELSKAP based?

KONE AKSJESELSKAP has its business address in Oslo.

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.