BIZTRAC BETA
Wholesale of other machinery and equipment

BJØRN JACOBSEN TRADING AS

Org. no. 990624747 Limited company (AS) Lørenskog Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 214,000
Equity NOK 4.5m
Incorporated 2006
Share capital NOK 100,000

BJØRN JACOBSEN TRADING AS is registered as a limited company in Lørenskog, Akershus with organisation number 990624747. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg, service og reparasjon av kraner og komponenter til industrien, samt kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 214,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 214,000
Equity
NOK 4.5m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns BJØRN JACOBSEN TRADING AS?

BJØRN JORULF JACOBSEN
BJØRN JACOBSEN TRADING AS
NOK 3.8m rev. · NOK 214,000 profit

BJØRN JACOBSEN TRADING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRN JACOBSEN TRADING AS

Who owns BJØRN JACOBSEN TRADING AS?

BJØRN JORULF JACOBSEN is the largest registered owner, with 100.0%.

What is the revenue of BJØRN JACOBSEN TRADING AS?

BJØRN JACOBSEN TRADING AS had revenue of NOK 3.8m in 2025.

Who is the general manager of BJØRN JACOBSEN TRADING AS?

Bjørn Jorulf Jacobsen is registered as general manager of BJØRN JACOBSEN TRADING AS.

Where is BJØRN JACOBSEN TRADING AS based?

BJØRN JACOBSEN TRADING AS has its business address in Fjellhamar.

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.