BIZTRAC BETA
Interior design activities

STUDIO VRENGEN AS

Org. no. 928848655 Limited company (AS) Arendal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK −57,000
Equity NOK 3,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

STUDIO VRENGEN AS is registered as a limited company in Arendal, Agder with organisation number 928848655. The business is classified under interior design activities (NACE 74.130). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Boligstyling, vareeksponering, dekoratørvirksomhet og alt som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK −57,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK −57,000
Equity
NOK 3,000
Est. value
NOK 1.7m

Financial health · 2024

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

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

Who owns STUDIO VRENGEN AS?

BERIT LARSEN VILDALEN
STUDIO VRENGEN AS
NOK 1.6m rev. · NOK −57,000 profit

STUDIO VRENGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STUDIO VRENGEN AS

Who owns STUDIO VRENGEN AS?

BERIT LARSEN VILDALEN is the largest registered owner, with 100.0%.

What is the revenue of STUDIO VRENGEN AS?

STUDIO VRENGEN AS had revenue of NOK 1.6m in 2024.

Who is the general manager of STUDIO VRENGEN AS?

Berit Larsen Vildalen is registered as general manager of STUDIO VRENGEN AS.

Where is STUDIO VRENGEN AS based?

STUDIO VRENGEN AS has its business address in Bjorbekk.

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.