BIZTRAC BETA
Activities auxiliary to insurance and pension funding n.e.c.

CJLIEN AS

Org. no. 923994734 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 54,000
Operating profit NOK −35,000
Equity NOK 43.8m
Incorporated 2019
Share capital NOK 100,000

Signals

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

CJLIEN AS is registered as a limited company in Bergen, Vestland with organisation number 923994734. The business is classified under activities auxiliary to insurance and pension funding n.e.c. (NACE 66.290). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Forsikringsrelaterte rådgivnings- og støttetjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 54,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2024

Revenue
NOK 54,000
Operating profit
NOK −35,000
Equity
NOK 43.8m
Est. value
NOK 26.5m

Financial health · 2024

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

Who owns CJLIEN AS?

CHRISTIAN JOHAN LIEN
CJLIEN AS
NOK 54,000 rev. · NOK −35,000 profit

CJLIEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CJLIEN AS own?

CJLIEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CJLIEN AS

Who owns CJLIEN AS?

CHRISTIAN JOHAN LIEN is the largest registered owner, with 100.0%.

What is the revenue of CJLIEN AS?

CJLIEN AS had revenue of NOK 54,000 in 2024.

Who is the general manager of CJLIEN AS?

Christian Johan Lien is registered as general manager of CJLIEN AS.

Where is CJLIEN AS based?

CJLIEN AS has its business address in Paradis.

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.