BIZTRAC BETA
Repair and maintenance of motor vehicles

KINDLISTUEN INVEST AS

Org. no. 932514087 Limited company (AS) Lillehammer Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 4.0m
Incorporated 2023
Share capital NOK 204,000

Signals

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

KINDLISTUEN INVEST AS is registered as a limited company in Lillehammer, Innlandet with organisation number 932514087. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2023. Registered share capital is NOK 204,000, divided into 40800 shares. The company's stated purpose is: “Investering i aksjer, andeler og andre formuesobjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 4.0m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns KINDLISTUEN INVEST AS?

ARNT HENNING HOEL KINDLISTUEN
KINDLISTUEN INVEST AS
NOK 0 rev. · NOK −15,000 profit

KINDLISTUEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KINDLISTUEN INVEST AS own?

KINDLISTUEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KINDLISTUEN INVEST AS

Who owns KINDLISTUEN INVEST AS?

ARNT HENNING HOEL KINDLISTUEN is the largest registered owner, with 100.0%.

What is the revenue of KINDLISTUEN INVEST AS?

KINDLISTUEN INVEST AS had revenue of NOK 0 in 2025.

Where is KINDLISTUEN INVEST AS based?

KINDLISTUEN INVEST AS has its business address in Lillehammer.

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.