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

BLOMEN VINJE AS

Org. no. 925581534 Limited company (AS) Vinje Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 123,000
Equity NOK 1.1m
Incorporated 2020
Employees 7
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-02-13 Adresseendring registrert 2026-02-13.

BLOMEN VINJE AS is registered as a limited company in Vinje, Telemark with organisation number 925581534. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2020 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Detaljhandel, produksjon og levering av tenester. Selskapet kan også delta som eigar i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 123,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 123,000
Equity
NOK 1.1m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns BLOMEN VINJE AS?

DANIEL HOLT
BLOMEN VINJE AS
NOK 3.8m rev. · NOK 123,000 profit

BLOMEN VINJE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLOMEN VINJE AS

Who owns BLOMEN VINJE AS?

DANIEL HOLT is the largest registered owner, with 100.0%.

What is the revenue of BLOMEN VINJE AS?

BLOMEN VINJE AS had revenue of NOK 3.8m in 2025.

Who is the general manager of BLOMEN VINJE AS?

Gunn Torfrid Bratland is registered as general manager of BLOMEN VINJE AS.

Where is BLOMEN VINJE AS based?

BLOMEN VINJE AS has its business address in Vinje.

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.