biztrac. BETA
COMPANY REGISTER PROFILE
920914888 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

KREUZINGER UND MANHART TURBULENZ GMBH NUF

Org. no. 920914888 Norwegian division of foreign business enterprise (NUF) Trondheim Active
Revenue 2025 NOK 1.5m
Operating profit NOK 58
Equity NOK 638

KREUZINGER UND MANHART TURBULENZ GMBH NUF is registered as a norwegian division of foreign business enterprise in Trondheim, Trøndelag with organisation number 920914888. The business is classified under computer programming activities (NACE 62.100). The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 58 in operating profit.

Former names: KREUZINGER UND MANHART TURBULENZ GMBH

Key figures · 2025

Revenue
NOK 1.5m
▲ +11 %
Operating profit
NOK 58
▼ −83 %
Equity
NOK 638
▼ −0 %
Est. value
NOK 761

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KREUZINGER UND MANHART TURBULENZ GMBH NUF?

No shareholders are registered for KREUZINGER UND MANHART TURBULENZ GMBH NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KREUZINGER UND MANHART TURBULENZ GMBH NUF

What is the revenue of KREUZINGER UND MANHART TURBULENZ GMBH NUF?

KREUZINGER UND MANHART TURBULENZ GMBH NUF had revenue of NOK 1.5m in 2025.

Who is the general manager of KREUZINGER UND MANHART TURBULENZ GMBH NUF?

Håkon Strandenes is registered as general manager of KREUZINGER UND MANHART TURBULENZ GMBH NUF.

Where is KREUZINGER UND MANHART TURBULENZ GMBH NUF based?

KREUZINGER UND MANHART TURBULENZ GMBH NUF has its business address in Trondheim.

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.