BIZTRAC BETA
Development of building projects

BERGEN INNOVATION AS

Org. no. 988110205 Limited company (AS) Øygarden Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 841,000
Operating profit NOK 383,000
Equity NOK 1.8m
Incorporated 2005
Share capital NOK 1.0m

Signals

1 flags
  • Nylig endring 2026-02-17 Adresseendring registrert 2026-02-17.

BERGEN INNOVATION AS is registered as a limited company in Øygarden, Vestland with organisation number 988110205. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering, utvikling og drift av eiendom. Samt investering i andre selskaper, pluss alt som faller naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 841,000 in revenue and NOK 383,000 in operating profit.

Key figures · 2024

Revenue
NOK 841,000
Operating profit
NOK 383,000
Equity
NOK 1.8m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns BERGEN INNOVATION AS?

TAGE FJÆREIDE
BERGEN INNOVATION AS
NOK 841,000 rev. · NOK 383,000 profit

BERGEN INNOVATION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN INNOVATION AS

Who owns BERGEN INNOVATION AS?

TAGE FJÆREIDE is the largest registered owner, with 100.0%.

What is the revenue of BERGEN INNOVATION AS?

BERGEN INNOVATION AS had revenue of NOK 841,000 in 2024.

Who is the general manager of BERGEN INNOVATION AS?

Tage Fjæreide is registered as general manager of BERGEN INNOVATION AS.

Where is BERGEN INNOVATION AS based?

BERGEN INNOVATION AS has its business address in Knarrevik.

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.