BIZTRAC BETA
Buying and selling of own real estate

PEGASUS INVEST I AS

Org. no. 912597393 Limited company (AS) Drammen Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −44,000
Equity NOK 4.1m
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−44k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PEGASUS INVEST I AS is registered as a limited company in Drammen, Buskerud with organisation number 912597393. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investerings- og holdingsvirksomhet og alt som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −44,000
Equity
NOK 4.1m
Est. value
NOK 4.1m

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.4%
Good
Equity as a share of total capital

Who owns PEGASUS INVEST I AS?

FIRE INVEST AS
PEGASUS INVEST I AS
· NOK −44,000 profit

PEGASUS INVEST I AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PEGASUS INVEST I AS own?

PEGASUS INVEST I AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

PEGASUS INVEST I AS er morselskap for 1 datterselskap:

Frequently asked questions about PEGASUS INVEST I AS

Who owns PEGASUS INVEST I AS?

FIRE INVEST AS is the largest registered owner, with 66.7%.

Who is the general manager of PEGASUS INVEST I AS?

Kai Egil Larsen is registered as general manager of PEGASUS INVEST I AS.

Where is PEGASUS INVEST I AS based?

PEGASUS INVEST I 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.