BIZTRAC BETA
Other captive investment companies

SCHWENNICKE AS

Org. no. 998298148 Limited company (AS) Haugesund Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 2.6m
Equity NOK 33.3m
Incorporated 2012
Share capital NOK 60,000

SCHWENNICKE AS is registered as a limited company in Haugesund, Rogaland with organisation number 998298148. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Eie og forvalte aksjer og andre verdipapirer, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 2.6m
Equity
NOK 33.3m
Est. value
NOK 26.2m

Financial health · 2025

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

Who owns SCHWENNICKE AS?

ARNE SCHWENNICKE
SCHWENNICKE AS
NOK 3.4m rev. · NOK 2.6m profit

SCHWENNICKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SCHWENNICKE AS own?

SCHWENNICKE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SCHWENNICKE AS

Who owns SCHWENNICKE AS?

ARNE SCHWENNICKE is the largest registered owner, with 100.0%.

What is the revenue of SCHWENNICKE AS?

SCHWENNICKE AS had revenue of NOK 3.4m in 2024.

Who is the general manager of SCHWENNICKE AS?

Arne Schwennicke is registered as general manager of SCHWENNICKE AS.

Where is SCHWENNICKE AS based?

SCHWENNICKE AS has its business address in Haugesund.

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.