BIZTRAC BETA
Other education activities

SCHWUNG AS

Org. no. 926370847 Limited company (AS) Sarpsborg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 215,000
Operating profit NOK −10,000
Equity NOK 2,000
Incorporated 2020
Share capital NOK 35,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

SCHWUNG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 926370847. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2020. Registered share capital is NOK 35,000, divided into 100000 shares. The company's stated purpose is: “Selge tjenester og varer innen kurs og rådgivning skole og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 215,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 215,000
Operating profit
NOK −10,000
Equity
NOK 2,000
Est. value
NOK 190,000

Financial health · 2024

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

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

Who owns SCHWUNG AS?

TOR SANDNES
SCHWUNG AS
NOK 215,000 rev. · NOK −10,000 profit

SCHWUNG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SCHWUNG AS

Who owns SCHWUNG AS?

TOR SANDNES is the largest registered owner, with 70.0%.

What is the revenue of SCHWUNG AS?

SCHWUNG AS had revenue of NOK 215,000 in 2024.

Who is the general manager of SCHWUNG AS?

Tor Sandnes is registered as general manager of SCHWUNG AS.

Where is SCHWUNG AS based?

SCHWUNG AS has its business address in Hafslundsøy.

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.