biztrac. BETA
COMPANY REGISTER PROFILE
912868575 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Industrial product and fashion design activities

HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF

Org. no. 912868575 Norwegian division of foreign business enterprise (NUF) Oslo Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 116,000
Equity NOK 988,000

HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF is registered as a norwegian division of foreign business enterprise in Oslo, Oslo with organisation number 912868575. The business is classified under industrial product and fashion design activities (NACE 74.110). The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 116,000 in operating profit.

Former names: HÄFELE GMBH & CO KG TYSKLAND FILIAL NORGE

Key figures · 2025

Revenue
NOK 2.4m
▼ −3 %
Operating profit
NOK 116,000
▼ −1 %
Equity
NOK 988,000
▲ +10 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
5.33
Very good
Current assets ÷ current liabilities
Profitability
10.2%
Good
Return on total assets
Solidity
81.2%
Very good
Equity as a share of total capital

Who owns HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF?

No shareholders are registered for HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF

What is the revenue of HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF?

HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF had revenue of NOK 2.4m in 2025.

Who is the general manager of HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF?

Christian Geissler is registered as general manager of HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF.

Where is HÄFELE SE & CO KG TYSKLAND FILIAL NORGE NUF based?

HÄFELE SE & CO KG TYSKLAND FILIAL NORGE 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.