BIZTRAC BETA
Manufacture of pharmaceutical preparations

GLYCANOVA AS

Org. no. 994035495 Limited company (AS) Fredrikstad Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −1.1m
Equity NOK −2.5m
Incorporated 2009
Share capital NOK 410,000

Signals

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

GLYCANOVA AS is registered as a limited company in Fredrikstad, Østfold with organisation number 994035495. The business is classified under manufacture of pharmaceutical preparations (NACE 21.200). The company was incorporated in 2009. Registered share capital is NOK 410,000, divided into 409943 shares. The company's stated purpose is: “Produksjon og salg av matvareprodukter og farmasøytika.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −1.1m
Equity
NOK −2.5m

Financial health · 2024

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

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

Who owns GLYCANOVA AS?

BJØRN KRISTIANSEN
GLYCANOVA AS
NOK 1.4m rev. · NOK −1.1m profit

GLYCANOVA AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about GLYCANOVA AS

Who owns GLYCANOVA AS?

BJØRN KRISTIANSEN is the largest registered owner, with 13.3%.

What is the revenue of GLYCANOVA AS?

GLYCANOVA AS had revenue of NOK 1.4m in 2024.

Who is the general manager of GLYCANOVA AS?

Lewis Linden Kristiansen is registered as general manager of GLYCANOVA AS.

Where is GLYCANOVA AS based?

GLYCANOVA AS has its business address in Gamle Fredrikstad.

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.