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

HEGGTOPPEN BLOMSTER AS

Org. no. 915447228 Limited company (AS) Lier Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 67,000
Equity NOK 38,000
Incorporated 2015
Employees 5
Share capital NOK 99,000

HEGGTOPPEN BLOMSTER AS is registered as a limited company in Lier, Buskerud with organisation number 915447228. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2015 and has 5 registered employees. Registered share capital is NOK 99,000, divided into 99 shares. The company's stated purpose is: “Detaljhandel blomster, interiør og planter.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 67,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 67,000
Equity
NOK 38,000
Est. value
NOK 237,000

Financial health · 2025

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.5%
Weak
Equity as a share of total capital

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

Who owns HEGGTOPPEN BLOMSTER AS?

TINA MARIE ERIKSEN
HEGGTOPPEN BLOMSTER AS
NOK 4.4m rev. · NOK 67,000 profit

HEGGTOPPEN BLOMSTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEGGTOPPEN BLOMSTER AS

Who owns HEGGTOPPEN BLOMSTER AS?

TINA MARIE ERIKSEN is the largest registered owner, with 92.9%.

What is the revenue of HEGGTOPPEN BLOMSTER AS?

HEGGTOPPEN BLOMSTER AS had revenue of NOK 4.4m in 2025.

Who is the general manager of HEGGTOPPEN BLOMSTER AS?

Tina Marie Eriksen is registered as general manager of HEGGTOPPEN BLOMSTER AS.

Where is HEGGTOPPEN BLOMSTER AS based?

HEGGTOPPEN BLOMSTER AS has its business address in Lier.

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.