BIZTRAC BETA
Industrial product and fashion design activities

VOLLANE DESIGNSTUDIO AS

Org. no. 935422914 Limited company (AS) Giske Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 304,000
Equity NOK 411,000
Incorporated 2025
Share capital NOK 30,000

VOLLANE DESIGNSTUDIO AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 935422914. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Designe, produsere, selge og distribuere miljøvennlige husholdningsartikler og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 304,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 304,000
Equity
NOK 411,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns VOLLANE DESIGNSTUDIO AS?

BIRGITTE LINDE RELLING
VOLLANE DESIGNSTUDIO AS
NOK 1.5m rev. · NOK 304,000 profit

VOLLANE DESIGNSTUDIO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VOLLANE DESIGNSTUDIO AS

Who owns VOLLANE DESIGNSTUDIO AS?

BIRGITTE LINDE RELLING is the largest registered owner, with 50.0%.

What is the revenue of VOLLANE DESIGNSTUDIO AS?

VOLLANE DESIGNSTUDIO AS had revenue of NOK 1.5m in 2025.

Who is the general manager of VOLLANE DESIGNSTUDIO AS?

Birgitte Linde Relling is registered as general manager of VOLLANE DESIGNSTUDIO AS.

Where is VOLLANE DESIGNSTUDIO AS based?

VOLLANE DESIGNSTUDIO AS has its business address in Vigra.

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.