biztrac. BETA
COMPANY REGISTER PROFILE
971552190 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of wood, construction materials and sanitary equipment

HANSGROHE SALGSKONTOR NUF

Org. no. 971552190 Norwegian division of foreign business enterprise (NUF) Oslo Active
Ownership graph ↗
Revenue 2025 NOK 60.1m
Operating profit NOK 151,000
Equity NOK 1.3m
Employees 7

HANSGROHE SALGSKONTOR NUF is registered as a norwegian division of foreign business enterprise in Oslo, Oslo with organisation number 971552190. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company has 7 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 60.1m in revenue and NOK 151,000 in operating profit.

Former names: GROHE HANS A/S C/O REG. REV. BENTE WILHELMSEN, GROHE HANS A/S C/O REG REV BENTE WILHELMSEN, GROHE HANS, HANS GROHE, HANS GROHE SALGSKONTOR

Key figures · 2025

Revenue
NOK 60.1m
▼ −1 %
Operating profit
NOK 151,000
▲ +115 %
Equity
NOK 1.3m
▲ +24 %
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
2.6%
Weak
Return on total assets
Solidity
10.7%
Satisfactory
Equity as a share of total capital

Who owns HANSGROHE SALGSKONTOR NUF?

No shareholders are registered for HANSGROHE SALGSKONTOR NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HANSGROHE SALGSKONTOR NUF

What is the revenue of HANSGROHE SALGSKONTOR NUF?

HANSGROHE SALGSKONTOR NUF had revenue of NOK 60.1m in 2025.

Who is the general manager of HANSGROHE SALGSKONTOR NUF?

Dan Rosendal is registered as general manager of HANSGROHE SALGSKONTOR NUF.

Where is HANSGROHE SALGSKONTOR NUF based?

HANSGROHE SALGSKONTOR NUF has its business address in Oslo.

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

Report a problem

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