BIZTRAC BETA
Plant propagation

MELLBYES PLANTESKOLE AS

Org. no. 913783603 Limited company (AS) Ringsaker Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 58.9m
Operating profit NOK 10.5m
Equity NOK 35.3m
Incorporated 2014
Employees 24
Share capital NOK 1.0m

MELLBYES PLANTESKOLE AS is registered as a limited company in Ringsaker, Innlandet with organisation number 913783603. The business is classified under plant propagation (NACE 01.300). The company was incorporated in 2014 and has 24 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Engrossalg av egenproduserte og innkjøpte planter og trær og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 58.9m in revenue and NOK 10.5m in operating profit.

Key figures · 2025

Revenue
NOK 58.9m
Operating profit
NOK 10.5m
Equity
NOK 35.3m
Est. value
NOK 51.2m

Financial health · 2025

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

Who owns MELLBYES PLANTESKOLE AS?

TORBJØRN MELLBYE 2 HOLDING AS
MELLBYES PLANTESKOLE AS
NOK 58.9m rev. · NOK 10.5m profit

MELLBYES PLANTESKOLE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MELLBYES PLANTESKOLE AS

Who owns MELLBYES PLANTESKOLE AS?

TORBJØRN MELLBYE 2 HOLDING AS is the largest registered owner, with 90.0%.

What is the revenue of MELLBYES PLANTESKOLE AS?

MELLBYES PLANTESKOLE AS had revenue of NOK 58.9m in 2025.

Who is the general manager of MELLBYES PLANTESKOLE AS?

Torbjørn Mellbye is registered as general manager of MELLBYES PLANTESKOLE AS.

Where is MELLBYES PLANTESKOLE AS based?

MELLBYES PLANTESKOLE AS has its business address in Nes På Hedmarken.

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.