biztrac. BETA
COMPANY REGISTER PROFILE
989859633 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other food

FEDON HELSE AS

Org. no. 989859633 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 6.4m
Operating profit NOK 727,000
Equity NOK −53,000
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−53k kr).

FEDON HELSE AS is registered as a limited company in Oslo, Oslo with organisation number 989859633. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selge helse- og næringsmiddelrelaterte varer og tjenester, samt alt som hermed er forbundet, herunder å delta i andre tilsvarende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.4m in revenue and NOK 727,000 in operating profit.

Former names: ALFANOR-E AS, EURODIET SCANDINAVIA AS

Key figures · 2025

Revenue
NOK 6.4m
▼ −20 %
Operating profit
NOK 727,000
▲ +168 %
Equity
NOK −53,000
▲ +93 %

Financial health · 2025

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
62.5%
Very good
Return on total assets
Solidity
-10.6%
Weak
Equity as a share of total capital

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

Who owns FEDON HELSE AS?

FEDON HELSE AS
NOK 6.4m rev. · NOK 727,000 profit

FEDON HELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FEDON HELSE AS

Who owns FEDON HELSE AS?

LINDBERG CONSULTING AS is the largest registered owner, with 100.0%.

What is the revenue of FEDON HELSE AS?

FEDON HELSE AS had revenue of NOK 6.4m in 2025.

Where is FEDON HELSE AS based?

FEDON HELSE 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 03.10.2026.

Report a problem

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