BIZTRAC BETA
Non-specialised wholesale trade

FERONIA NORDIC AS

Org. no. 821270332 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −46,000
Equity NOK −1.9m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

FERONIA NORDIC AS is registered as a limited company in Oslo, Oslo with organisation number 821270332. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 60000 shares. The company's stated purpose is: “Kjøp og salg av helserelaterte produkter. Tjenesteytende opplysningsvirksomhet ved bruk av helserelaterte produkter. Deltakelse i andre selskaper og annet som står i denne forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −46,000
Equity
NOK −1.9m

Financial health · 2024

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

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

Who owns FERONIA NORDIC AS?

NUTRA INVEST AS
FERONIA NORDIC AS
NOK 0 rev. · NOK −46,000 profit

FERONIA NORDIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FERONIA NORDIC AS

Who owns FERONIA NORDIC AS?

NUTRA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of FERONIA NORDIC AS?

FERONIA NORDIC AS had revenue of NOK 0 in 2024.

Where is FERONIA NORDIC AS based?

FERONIA NORDIC AS has its business address in Oslo.

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.