biztrac. BETA
COMPANY REGISTER PROFILE
983641350 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

PUBGENE AS

Org. no. 983641350 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −2.6m
Equity NOK 16.4m
Incorporated 2001
Share capital NOK 288,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,6 mill kr).

PUBGENE AS is registered as a limited company in Oslo, Oslo with organisation number 983641350. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2001. Registered share capital is NOK 288,000, divided into 287500 shares. The company's stated purpose is: “Selge, utvikle og kommersialisere metoder, tjenester og produkter innenfor bioteknologi og Internett.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −2.6m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
▼ −23 %
Operating profit
NOK −2.6m
▼ −135 %
Equity
NOK 16.4m
▼ −13 %
Est. value
NOK 11.2m

Financial health · 2025

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
-9.6%
Not satisfactory
Return on total assets
Solidity
66.5%
Very good
Equity as a share of total capital

Who owns PUBGENE AS?

PUBGENE INC US
PUBGENE AS
NOK 2.2m rev. · NOK −2.6m profit

PUBGENE AS has 1 registered shareholder:

  • PUBGENE INC 100.0%
All shareholders and roles →

Frequently asked questions about PUBGENE AS

Who owns PUBGENE AS?

PUBGENE INC is the largest registered owner, with 100.0%.

What is the revenue of PUBGENE AS?

PUBGENE AS had revenue of NOK 2.2m in 2025.

Who is the general manager of PUBGENE AS?

Håvard Hildeng Hauge is registered as general manager of PUBGENE AS.

Where is PUBGENE AS based?

PUBGENE 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.