BIZTRAC BETA
COMPANY REGISTER PROFILE
965245820 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Wholesale of hardware, plumbing and heating equipment and supplies

BLÜCHER NORWAY AS

Org. no. 965245820 Limited company (AS) Siljan Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 57.2m
Operating profit NOK 4.8m
Equity NOK 10.4m
Incorporated 1992
Employees 7
Share capital NOK 1.0m

BLÜCHER NORWAY AS is registered as a limited company in Siljan, Telemark with organisation number 965245820. The business is classified under wholesale of hardware, plumbing and heating equipment and supplies (NACE 46.840). The company was incorporated in 1992 and has 7 registered employees. Registered share capital is NOK 1.0m. The company's stated purpose is: “Kjøp og salg av rustfrie artikler og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 57.2m in revenue and NOK 4.8m in operating profit.

Former names: BLUCHER AS

Key figures · 2025

Revenue
NOK 57.2m
Operating profit
NOK 4.8m
Equity
NOK 10.4m
Est. value
NOK 22.0m

Financial health · 2025

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.7%
Good
Equity as a share of total capital

Who owns BLÜCHER NORWAY AS?

BLÜCHER NORWAY AS
NOK 57.2m rev. · NOK 4.8m profit

BLÜCHER NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLÜCHER NORWAY AS

Who owns BLÜCHER NORWAY AS?

BLÜCHER METAL A/S is the largest registered owner, with 100.0%.

What is the revenue of BLÜCHER NORWAY AS?

BLÜCHER NORWAY AS had revenue of NOK 57.2m in 2025.

Who is the general manager of BLÜCHER NORWAY AS?

Torstein Røsholt is registered as general manager of BLÜCHER NORWAY AS.

Where is BLÜCHER NORWAY AS based?

BLÜCHER NORWAY AS has its business address in Siljan.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.