BIZTRAC BETA
Repair and maintenance of motor vehicles

BERGEN ANTIRUST AS

Org. no. 918868879 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK −46,000
Equity NOK −475,000
Incorporated 2017
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−475k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

BERGEN ANTIRUST AS is registered as a limited company in Bergen, Vestland with organisation number 918868879. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2017 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Understellsbehandling av person og lastebil og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK −46,000
Equity
NOK −475,000

Financial health · 2024

Liquidity
0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-132.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BERGEN ANTIRUST AS?

STIG OVE JACOBSEN
BERGEN ANTIRUST AS
NOK 4.1m rev. · NOK −46,000 profit

BERGEN ANTIRUST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGEN ANTIRUST AS

Who owns BERGEN ANTIRUST AS?

STIG OVE JACOBSEN is the largest registered owner, with 60.0%.

What is the revenue of BERGEN ANTIRUST AS?

BERGEN ANTIRUST AS had revenue of NOK 4.1m in 2024.

Where is BERGEN ANTIRUST AS based?

BERGEN ANTIRUST AS has its business address in Nyborg.

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.