BIZTRAC BETA
Manufacture of weapons and ammunition

BØRSEMAKER TOR SOLBERG AS

Org. no. 926886584 Limited company (AS) Indre Østfold Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 94,000
Equity NOK 868,000
Incorporated 2021
Share capital NOK 30,000

BØRSEMAKER TOR SOLBERG AS is registered as a limited company in Indre Østfold, Østfold with organisation number 926886584. The business is classified under manufacture of weapons and ammunition (NACE 25.300). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Børsemakervirksomhet, utleie av utstyr, mannskap og det som faller naturlig til dette. Viltforvaltning og det som faller naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 94,000
Equity
NOK 868,000
Est. value
NOK 916,000

Financial health · 2025

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

Who owns BØRSEMAKER TOR SOLBERG AS?

TOR SOLBERG
BØRSEMAKER TOR SOLBERG AS
NOK 1.3m rev. · NOK 94,000 profit

BØRSEMAKER TOR SOLBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BØRSEMAKER TOR SOLBERG AS

Who owns BØRSEMAKER TOR SOLBERG AS?

TOR SOLBERG is the largest registered owner, with 100.0%.

What is the revenue of BØRSEMAKER TOR SOLBERG AS?

BØRSEMAKER TOR SOLBERG AS had revenue of NOK 1.3m in 2025.

Who is the general manager of BØRSEMAKER TOR SOLBERG AS?

Tor Solberg is registered as general manager of BØRSEMAKER TOR SOLBERG AS.

Where is BØRSEMAKER TOR SOLBERG AS based?

BØRSEMAKER TOR SOLBERG AS has its business address in Askim.

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.