BIZTRAC BETA
Business and other management consultancy activities

BIOFERTILIZE AS

Org. no. 831463872 Limited company (AS) Molde Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −78,000
Equity NOK −93,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−93k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−78k kr).

BIOFERTILIZE AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 831463872. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle gjødsel konsepter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −78,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −78,000
Equity
NOK −93,000

Financial health · 2025

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-326.2%
Weak
Equity as a share of total capital

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

Who owns BIOFERTILIZE AS?

MPT HOLDING AS
BIOFERTILIZE AS
NOK 0 rev. · NOK −78,000 profit

BIOFERTILIZE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIOFERTILIZE AS

Who owns BIOFERTILIZE AS?

MPT HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of BIOFERTILIZE AS?

BIOFERTILIZE AS had revenue of NOK 0 in 2025.

Who is the general manager of BIOFERTILIZE AS?

Børge Rød is registered as general manager of BIOFERTILIZE AS.

Where is BIOFERTILIZE AS based?

BIOFERTILIZE AS has its business address in Eresfjord.

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.