BIZTRAC BETA
COMPANY REGISTER PROFILE
928950131 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

REALLY BAD INVESTMENTS AS

Org. no. 928950131 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −12
Equity NOK −90,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−90k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12 kr).

REALLY BAD INVESTMENTS AS is registered as a limited company in Stavanger, Rogaland with organisation number 928950131. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og investeringer i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −12
Equity
NOK −90,000

Financial health · 2025

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

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

Who owns REALLY BAD INVESTMENTS AS?

REALLY BAD INVESTMENTS AS
· NOK −12 profit

REALLY BAD INVESTMENTS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REALLY BAD INVESTMENTS AS own?

REALLY BAD INVESTMENTS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REALLY BAD INVESTMENTS AS

Who owns REALLY BAD INVESTMENTS AS?

Philip Maxime Hartell is the largest registered owner, with 100.0%.

Who is the general manager of REALLY BAD INVESTMENTS AS?

Philip Maxime Hartell is registered as general manager of REALLY BAD INVESTMENTS AS.

Where is REALLY BAD INVESTMENTS AS based?

REALLY BAD INVESTMENTS AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.