BIZTRAC BETA
Repair and maintenance of fabricated metal products

BØRSEMAKER SVARTVATN AS

Org. no. 913308077 Limited company (AS) Hemnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 166,000
Operating profit NOK 29,000
Equity NOK 183,000
Incorporated 2014
Share capital NOK 30,000

BØRSEMAKER SVARTVATN AS is registered as a limited company in Hemnes, Nordland with organisation number 913308077. The business is classified under repair and maintenance of fabricated metal products (NACE 33.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Reparasjon og salg av ulike typer håndvåpen, her under også annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 166,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 166,000
Operating profit
NOK 29,000
Equity
NOK 183,000
Est. value
NOK 208,000

Financial health · 2025

Liquidity
27.86
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 BØRSEMAKER SVARTVATN AS?

ARNFINN SVARTVATN
BØRSEMAKER SVARTVATN AS
NOK 166,000 rev. · NOK 29,000 profit

BØRSEMAKER SVARTVATN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BØRSEMAKER SVARTVATN AS

Who owns BØRSEMAKER SVARTVATN AS?

ARNFINN SVARTVATN is the largest registered owner, with 50.0%.

What is the revenue of BØRSEMAKER SVARTVATN AS?

BØRSEMAKER SVARTVATN AS had revenue of NOK 166,000 in 2025.

Who is the general manager of BØRSEMAKER SVARTVATN AS?

Arnfinn Svartvatn is registered as general manager of BØRSEMAKER SVARTVATN AS.

Where is BØRSEMAKER SVARTVATN AS based?

BØRSEMAKER SVARTVATN AS has its business address in Finneidfjord.

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.