BIZTRAC BETA
Computer programming activities

CHILITECH AS

Org. no. 926524984 Limited company (AS) Sandefjord Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 94,000
Operating profit NOK −10,000
Equity NOK 86,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

CHILITECH AS is registered as a limited company in Sandefjord, Vestfold with organisation number 926524984. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Programvareutvikling, investeringer i andre foretak og investering i eiendom for øvrig, rådgivning innen e-handel, programvareutvikling og varehandel.”. The most recent filed accounts, for the 2024 financial year, show NOK 94,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 94,000
Operating profit
NOK −10,000
Equity
NOK 86,000
Est. value
NOK 198,000

Financial health · 2024

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

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

Who owns CHILITECH AS?

YUNPENG HAN
CHILITECH AS
NOK 94,000 rev. · NOK −10,000 profit

CHILITECH AS has 3 registered shareholders:

All shareholders and roles →

Which companies does CHILITECH AS own?

CHILITECH AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CHILITECH AS

Who owns CHILITECH AS?

YUNPENG HAN is the largest registered owner, with 33.3%.

What is the revenue of CHILITECH AS?

CHILITECH AS had revenue of NOK 94,000 in 2024.

Where is CHILITECH AS based?

CHILITECH AS has its business address in Sandefjord.

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.