BIZTRAC BETA
Organisation of conventions and trade shows

FIRST TUESDAY BERGEN AS

Org. no. 983981631 Limited company (AS) Bergen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 605,000
Operating profit NOK 352,000
Equity NOK 101,000
Incorporated 2001
Share capital NOK 100,000

FIRST TUESDAY BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 983981631. The business is classified under organisation of conventions and trade shows (NACE 82.300). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 300 shares. The company's stated purpose is: “Å skape forretningsmessige muligheter ved å koble mennesker, idèer, kapital og tjenester i nettverk innen IKT-næringen herunder arrangement av konferanser, seminarer, salg av konsulenttjenester, jobbformidling, eierskap og lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 605,000 in revenue and NOK 352,000 in operating profit.

Key figures · 2025

Revenue
NOK 605,000
Operating profit
NOK 352,000
Equity
NOK 101,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns FIRST TUESDAY BERGEN AS?

HANACKC HOLDING AS
FIRST TUESDAY BERGEN AS
NOK 605,000 rev. · NOK 352,000 profit

FIRST TUESDAY BERGEN AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about FIRST TUESDAY BERGEN AS

Who owns FIRST TUESDAY BERGEN AS?

HANACKC HOLDING AS is the largest registered owner, with 20.0%.

What is the revenue of FIRST TUESDAY BERGEN AS?

FIRST TUESDAY BERGEN AS had revenue of NOK 605,000 in 2025.

Where is FIRST TUESDAY BERGEN AS based?

FIRST TUESDAY BERGEN AS has its business address in Bønes.

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.