BIZTRAC BETA
Other building and industrial cleaning activities

DANIELS VINDUSPUSS AS

Org. no. 998467438 Limited company (AS) Narvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 99,000
Equity NOK 451,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-17 Adresseendring registrert 2026-03-17.

DANIELS VINDUSPUSS AS is registered as a limited company in Narvik, Nordland with organisation number 998467438. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvendig rengjøring av bygninger og industriell rengjøring. Import renholdsartikler.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 99,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 99,000
Equity
NOK 451,000
Est. value
NOK 711,000

Financial health · 2025

Liquidity
2.74
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
67.4%
Very good
Equity as a share of total capital

Who owns DANIELS VINDUSPUSS AS?

DANIEL BENTZEN
DANIELS VINDUSPUSS AS
NOK 2.9m rev. · NOK 99,000 profit

DANIELS VINDUSPUSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DANIELS VINDUSPUSS AS

Who owns DANIELS VINDUSPUSS AS?

DANIEL BENTZEN is the largest registered owner, with 100.0%.

What is the revenue of DANIELS VINDUSPUSS AS?

DANIELS VINDUSPUSS AS had revenue of NOK 2.9m in 2025.

Who is the general manager of DANIELS VINDUSPUSS AS?

Daniel Bentzen is registered as general manager of DANIELS VINDUSPUSS AS.

Where is DANIELS VINDUSPUSS AS based?

DANIELS VINDUSPUSS AS has its business address in Ankenes.

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.