BIZTRAC BETA
Arts creation activities in literature

VIRVELVINDER AS

Org. no. 931059068 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 158,000
Operating profit NOK 6,000
Equity NOK 38,000
Incorporated 2023
Share capital NOK 30,000

VIRVELVINDER AS is registered as a limited company in Oslo, Oslo with organisation number 931059068. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen innholdsproduksjon på sosiale medier - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 158,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 158,000
Operating profit
NOK 6,000
Equity
NOK 38,000
Est. value
NOK 50,000

Financial health · 2025

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

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

Who owns VIRVELVINDER AS?

JONAS FELDE SEVALDRUD
VIRVELVINDER AS
NOK 158,000 rev. · NOK 6,000 profit

VIRVELVINDER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIRVELVINDER AS

Who owns VIRVELVINDER AS?

JONAS FELDE SEVALDRUD is the largest registered owner, with 100.0%.

What is the revenue of VIRVELVINDER AS?

VIRVELVINDER AS had revenue of NOK 158,000 in 2025.

Who is the general manager of VIRVELVINDER AS?

Jonas Felde Sevaldrud is registered as general manager of VIRVELVINDER AS.

Where is VIRVELVINDER AS based?

VIRVELVINDER AS has its business address in Oslo.

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.