BIZTRAC BETA
Uoppgitt

KLILLE AS

Org. no. 932871882 Limited company (AS) Porsgrunn Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 12,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

KLILLE AS is registered as a limited company in Porsgrunn, Telemark with organisation number 932871882. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer og investere i virksomheter av enhver art, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 12,000
Est. value
NOK 14,000

Financial health · 2025

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.3%
Weak
Equity as a share of total capital

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

Who owns KLILLE AS?

KAROLINE MØRCH LILLEDRANGE
KLILLE AS
NOK 0 rev. · NOK −12,000 profit

KLILLE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KLILLE AS own?

KLILLE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLILLE AS

Who owns KLILLE AS?

KAROLINE MØRCH LILLEDRANGE is the largest registered owner, with 100.0%.

What is the revenue of KLILLE AS?

KLILLE AS had revenue of NOK 0 in 2025.

Who is the general manager of KLILLE AS?

Karoline Mørch Lilledrange is registered as general manager of KLILLE AS.

Where is KLILLE AS based?

KLILLE AS has its business address in Porsgrunn.

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.