BIZTRAC BETA
Rental and leasing of other personal and household goods

DRØMMEBLOMSTER AS

Org. no. 934178092 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 19,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

DRØMMEBLOMSTER AS is registered as a limited company in Oslo, Oslo with organisation number 934178092. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie og salg av dekorasjoner med mer til arbeidsmiljø og eventer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 19,000
Est. value
NOK 27,000

Financial health · 2025

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

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

Who owns DRØMMEBLOMSTER AS?

EGROUP NORWAY AS
DRØMMEBLOMSTER AS
NOK 0 rev. · NOK −5,000 profit

DRØMMEBLOMSTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRØMMEBLOMSTER AS

Who owns DRØMMEBLOMSTER AS?

EGROUP NORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of DRØMMEBLOMSTER AS?

DRØMMEBLOMSTER AS had revenue of NOK 0 in 2025.

Who is the general manager of DRØMMEBLOMSTER AS?

Petter Eriksen is registered as general manager of DRØMMEBLOMSTER AS.

Where is DRØMMEBLOMSTER AS based?

DRØMMEBLOMSTER AS has its business address in Oslo.

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.