BIZTRAC BETA
Uoppgitt

LYCHE PROSJEKTER AS

Org. no. 921660332 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK 218,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

LYCHE PROSJEKTER AS is registered as a limited company in Drammen, Buskerud with organisation number 921660332. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringer i foretak eller virksomhet, herunder men ikke begrenset til medvirkning i som eier i andre selskaper, salgsagentvirksomhet, utlånsvirksomhet eller andre gode forretningsideer som gir god uttelling til lav innsats.”.

Key figures · 2025

Operating profit
NOK −19,000
Equity
NOK 218,000
Est. value
NOK 729,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.5%
Satisfactory
Equity as a share of total capital

Who owns LYCHE PROSJEKTER AS?

HEIDI CATHRINE SCHRØTER LYCHE
LYCHE PROSJEKTER AS
· NOK −19,000 profit

LYCHE PROSJEKTER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYCHE PROSJEKTER AS own?

LYCHE PROSJEKTER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYCHE PROSJEKTER AS

Who owns LYCHE PROSJEKTER AS?

HEIDI CATHRINE SCHRØTER LYCHE is the largest registered owner, with 100.0%.

Who is the general manager of LYCHE PROSJEKTER AS?

Heidi Cathrine Schrøter Lyche is registered as general manager of LYCHE PROSJEKTER AS.

Where is LYCHE PROSJEKTER AS based?

LYCHE PROSJEKTER AS has its business address in Drammen.

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.