biztrac. BETA
COMPANY REGISTER PROFILE
930758531 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Motion picture, video and television programme production activities

VETLE SEVILD AS

Org. no. 930758531 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 322,000
Operating profit NOK −5,000
Equity NOK 26,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

VETLE SEVILD AS is registered as a limited company in Tromsø, Troms with organisation number 930758531. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon av film og foto.”. The most recent filed accounts, for the 2025 financial year, show NOK 322,000 in revenue and NOK −5,000 in operating profit.

Former names: UTHUSET FILM OG FOTO AS

Key figures · 2025

Revenue
NOK 322,000
▼ −49 %
Operating profit
NOK −5,000
▼ −180 %
Equity
NOK 26,000
▼ −20 %
Est. value
NOK 16,000

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
-7.3%
Not satisfactory
Return on total assets
Solidity
43.6%
Weak
Equity as a share of total capital

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

Who owns VETLE SEVILD AS?

VETLE SEVILD AS
NOK 322,000 rev. · NOK −5,000 profit

VETLE SEVILD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VETLE SEVILD AS

Who owns VETLE SEVILD AS?

Vetle Sevild is the largest registered owner, with 100.0%.

What is the revenue of VETLE SEVILD AS?

VETLE SEVILD AS had revenue of NOK 322,000 in 2025.

Where is VETLE SEVILD AS based?

VETLE SEVILD AS has its business address in Tromsø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.