BIZTRAC BETA
Architectural activities

OPUS BERGEN AS

Org. no. 921610602 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 35.4m
Operating profit NOK 6.5m
Equity NOK 1.7m
Incorporated 2018
Employees 19
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OPUS BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 921610602. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2018 and has 19 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Samfunnsplanlegging og rådgivning innen privat og offentlig sektor og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.4m in revenue and NOK 6.5m in operating profit.

Key figures · 2024

Revenue
NOK 35.4m
Operating profit
NOK 6.5m
Equity
NOK 1.7m
Est. value
NOK 29.4m

Financial health · 2024

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns OPUS BERGEN AS?

OPUS BERGEN HOLDING AS
OPUS BERGEN AS
NOK 35.4m rev. · NOK 6.5m profit

OPUS BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPUS BERGEN AS

Who owns OPUS BERGEN AS?

OPUS BERGEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OPUS BERGEN AS?

OPUS BERGEN AS had revenue of NOK 35.4m in 2024.

Who is the general manager of OPUS BERGEN AS?

Nancy Irene Jøssang is registered as general manager of OPUS BERGEN AS.

Where is OPUS BERGEN AS based?

OPUS BERGEN AS has its business address in Bergen.

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.