BIZTRAC BETA
Visual arts creation activities

MAHO BLOMSTER AS

Org. no. 922302413 Limited company (AS) Malvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 187,000
Equity NOK 78,000
Incorporated 2019
Share capital NOK 100,000

MAHO BLOMSTER AS is registered as a limited company in Malvik, Trøndelag with organisation number 922302413. The business is classified under visual arts creation activities (NACE 90.120). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentarbeid og dekoroppdrag med blomster og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 187,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 187,000
Equity
NOK 78,000
Est. value
NOK 880,000

Financial health · 2024

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

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

Who owns MAHO BLOMSTER AS?

MARIANN HOLMEN
MAHO BLOMSTER AS
NOK 1.1m rev. · NOK 187,000 profit

MAHO BLOMSTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAHO BLOMSTER AS

Who owns MAHO BLOMSTER AS?

MARIANN HOLMEN is the largest registered owner, with 80.0%.

What is the revenue of MAHO BLOMSTER AS?

MAHO BLOMSTER AS had revenue of NOK 1.1m in 2024.

Where is MAHO BLOMSTER AS based?

MAHO BLOMSTER AS has its business address in Hommelvik.

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.