BIZTRAC BETA
Retail sale of flowers, plants, seeds and fertilisers

DAMPLASS BLOMSTER AS

Org. no. 990038988 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 34,000
Equity NOK 399,000
Incorporated 2006
Employees 7
Share capital NOK 100,000

DAMPLASS BLOMSTER AS is registered as a limited company in Oslo, Oslo with organisation number 990038988. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2006 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Salg av varer, blomster og dertil egnede artikler. Deltakelse i andre selskaper, samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 34,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 34,000
Equity
NOK 399,000
Est. value
NOK 288,000

Financial health · 2024

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

Who owns DAMPLASS BLOMSTER AS?

LARS YESMIR BINGEN
DAMPLASS BLOMSTER AS
NOK 4.1m rev. · NOK 34,000 profit

DAMPLASS BLOMSTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DAMPLASS BLOMSTER AS

Who owns DAMPLASS BLOMSTER AS?

LARS YESMIR BINGEN is the largest registered owner, with 50.0%.

What is the revenue of DAMPLASS BLOMSTER AS?

DAMPLASS BLOMSTER AS had revenue of NOK 4.1m in 2024.

Who is the general manager of DAMPLASS BLOMSTER AS?

Polymnia Papadopoulou is registered as general manager of DAMPLASS BLOMSTER AS.

Where is DAMPLASS BLOMSTER AS based?

DAMPLASS BLOMSTER 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.