biztrac. BETA
COMPANY REGISTER PROFILE
918993975 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

FRUITZONE AS

Org. no. 918993975 Limited company (AS) Kristiansand Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 125,000
Incorporated 2017
Share capital NOK 216,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FRUITZONE AS is registered as a limited company in Kristiansand, Agder with organisation number 918993975. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 216,000, divided into 216000 shares. The company's stated purpose is: “Kjøp, salg og forvalting av eiendom, og aktiviteter som naturlig måtte falle inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Former names: BY NORDIC PRINT AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
▼ −4 %
Equity
NOK 125,000
▼ −12 %
Est. value
NOK 114,000

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
-2.5%
Not satisfactory
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns FRUITZONE AS?

FRUITZONE AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRUITZONE AS

Who owns FRUITZONE AS?

JRM HOLDING AS is the largest registered owner, with 55.0%.

What is the revenue of FRUITZONE AS?

FRUITZONE AS had revenue of NOK 0 in 2025.

Where is FRUITZONE AS based?

FRUITZONE AS has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.