BIZTRAC BETA
Research and experimental development on natural sciences and engineering

BIOSERGEN AS

Org. no. 987622075 Limited company (AS) Trondheim Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 75,000
Operating profit NOK −10.0m
Equity NOK 5.4m
Incorporated 2004
Share capital NOK 4.3m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10,0 mill kr).

BIOSERGEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 987622075. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2004. Registered share capital is NOK 4.3m, divided into 33457248 shares. The company's stated purpose is: “Forskning, utvikling, kommersialisering, produksjon og salg av bioteknologi og medisiner, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 75,000 in revenue and NOK −10.0m in operating profit.

Key figures · 2024

Revenue
NOK 75,000
Operating profit
NOK −10.0m
Equity
NOK 5.4m
Est. value
NOK 2.7m

Financial health · 2024

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.7%
Good
Equity as a share of total capital

Who owns BIOSERGEN AS?

BIOSERGEN AB
BIOSERGEN AS
NOK 75,000 rev. · NOK −10.0m profit

BIOSERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIOSERGEN AS

Who owns BIOSERGEN AS?

BIOSERGEN AB is the largest registered owner, with 100.0%.

What is the revenue of BIOSERGEN AS?

BIOSERGEN AS had revenue of NOK 75,000 in 2024.

Who is the general manager of BIOSERGEN AS?

Niels Laursen is registered as general manager of BIOSERGEN AS.

Where is BIOSERGEN AS based?

BIOSERGEN AS has its business address in Tiller.

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.