BIZTRAC BETA
Research and experimental development on natural sciences and engineering

FRUKT AS

Org. no. 923365001 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 234,000
Operating profit NOK −310,000
Equity NOK −381,000
Incorporated 2019
Share capital NOK 37,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−381k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−310k kr).

FRUKT AS is registered as a limited company in Asker, Akershus with organisation number 923365001. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2019. Registered share capital is NOK 37,000, divided into 37200 shares. The company's stated purpose is: “Tilby innovative og miljøvennlige løsninger til fruktproduksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 234,000 in revenue and NOK −310,000 in operating profit.

Key figures · 2024

Revenue
NOK 234,000
Operating profit
NOK −310,000
Equity
NOK −381,000

Financial health · 2024

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

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

Who owns FRUKT AS?

EDCA05 AS
FRUKT AS
NOK 234,000 rev. · NOK −310,000 profit

FRUKT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRUKT AS

Who owns FRUKT AS?

EDCA05 AS is the largest registered owner, with 72.6%.

What is the revenue of FRUKT AS?

FRUKT AS had revenue of NOK 234,000 in 2024.

Who is the general manager of FRUKT AS?

Morten Blaauw is registered as general manager of FRUKT AS.

Where is FRUKT AS based?

FRUKT AS has its business address in Sætre.

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.