biztrac. BETA
COMPANY REGISTER PROFILE
921484437 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

SCHWEITZ HOLDING AS

Org. no. 921484437 Limited company (AS) Asker Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 96,000
Operating profit NOK −465,000
Equity NOK 8.9m
Incorporated 2018
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−465k kr).

SCHWEITZ HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 921484437. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Investeringsselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 96,000 in revenue and NOK −465,000 in operating profit.

Key figures · 2025

Revenue
NOK 96,000
▼ −12 %
Operating profit
NOK −465,000
▲ +38 %
Equity
NOK 8.9m
▼ −3 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
-1.9%
Not satisfactory
Return on total assets
Solidity
67.7%
Very good
Equity as a share of total capital

Who owns SCHWEITZ HOLDING AS?

SCHWEITZ HOLDING AS
NOK 96,000 rev. · NOK −465,000 profit

SCHWEITZ HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SCHWEITZ HOLDING AS own?

SCHWEITZ HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SCHWEITZ HOLDING AS

Who owns SCHWEITZ HOLDING AS?

Jesper Rutting Schweitz is the largest registered owner, with 100.0%.

What is the revenue of SCHWEITZ HOLDING AS?

SCHWEITZ HOLDING AS had revenue of NOK 96,000 in 2025.

Where is SCHWEITZ HOLDING AS based?

SCHWEITZ HOLDING AS has its business address in Asker.

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.