biztrac. BETA
COMPANY REGISTER PROFILE
917373566 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠KJOS EIGEDOM AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Buying and selling of own real estate

KJOS EIGEDOM AS

Org. no. 917373566 Limited company (AS) Luster Incorporated 2016 In liquidation
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK 2.0m
Incorporated 2016
Share capital NOK 30,000

Signals

4 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-10-06 Under avvikling registrert 2026-10-06.

KJOS EIGEDOM AS is registered as a limited company in Luster, Vestland with organisation number 917373566. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å kjøpe, oppføre, eie og selge fast eiendom samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −19,000
▼ −37 %
Equity
NOK 2.0m
▲ +3 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
136.93
Very good
Current assets ÷ current liabilities
Profitability
3.4%
Weak
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns KJOS EIGEDOM AS?

KJOS EIGEDOM AS
· NOK −19,000 profit

KJOS EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJOS EIGEDOM AS

Who owns KJOS EIGEDOM AS?

TØMRAR LARS ERIK KJOS AS is the largest registered owner, with 100.0%.

Where is KJOS EIGEDOM AS based?

KJOS EIGEDOM AS has its business address in Hafslo.

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.