BIZTRAC BETA
Computer consultancy and computer facilities management activities

WILTING HOLDING AS

Org. no. 922264716 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2019
Share capital NOK 30,000

WILTING HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 922264716. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer, samt delta i andre selskaper. Selskapet kan også drive med konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 54,000

Financial health · 2025

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

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

Who owns WILTING HOLDING AS?

SINDRE ALSTAD WILTING
WILTING HOLDING AS
NOK 0 rev. · NOK 0 profit

WILTING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WILTING HOLDING AS

Who owns WILTING HOLDING AS?

SINDRE ALSTAD WILTING is the largest registered owner, with 100.0%.

What is the revenue of WILTING HOLDING AS?

WILTING HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of WILTING HOLDING AS?

Sindre Alstad Wilting is registered as general manager of WILTING HOLDING AS.

Where is WILTING HOLDING AS based?

WILTING HOLDING AS has its business address in Mjøndalen.

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.