biztrac. BETA
COMPANY REGISTER PROFILE
919216360 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

ARNE K LIER AS

Org. no. 919216360 Limited company (AS) Aurskog-Høland Incorporated 2017 Active
Revenue 2025 NOK 0
Operating profit NOK −76,000
Equity NOK 37,000
Incorporated 2017
Share capital NOK 50,000

Signals

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

ARNE K LIER AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 919216360. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Maskinentreprenør, sikkerhetstjeneste innenfor jernbane og alt som står i naturlig forbindelse med dette. i tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −76,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −76,000
▼ −740 %
Equity
NOK 37,000
▼ −67 %
Est. value
NOK 38,000

Financial health · 2025

Liquidity
0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
-60.1%
Not satisfactory
Return on total assets
Solidity
44.0%
Weak
Equity as a share of total capital

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

Who owns ARNE K LIER AS?

ARNE K LIER AS
NOK 0 rev. · NOK −76,000 profit

ARNE K LIER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARNE K LIER AS

Who owns ARNE K LIER AS?

KONGTORP HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ARNE K LIER AS?

ARNE K LIER AS had revenue of NOK 0 in 2025.

Where is ARNE K LIER AS based?

ARNE K LIER AS has its business address in Bjørkelangen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.