BIZTRAC BETA
Rental and operating of own or leased real estate

ARBITRAGE AS

Org. no. 893160582 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 255,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

ARBITRAGE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 893160582. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsvirksomhet og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 255,000
Est. value
NOK 232,000

Financial health · 2025

Liquidity
4.09
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.4%
Very good
Equity as a share of total capital

Who owns ARBITRAGE AS?

STIG JACOBSEN
ARBITRAGE AS
NOK 0 rev. · NOK −8,000 profit

ARBITRAGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARBITRAGE AS own?

ARBITRAGE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ARBITRAGE AS

Who owns ARBITRAGE AS?

STIG JACOBSEN is the largest registered owner, with 100.0%.

What is the revenue of ARBITRAGE AS?

ARBITRAGE AS had revenue of NOK 0 in 2025.

Where is ARBITRAGE AS based?

ARBITRAGE AS has its business address in Trondheim.

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.