BIZTRAC BETA
Motion picture, video and television programme production activities

SIIVET AS

Org. no. 991172181 Limited company (AS) Porsanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −50,000
Equity NOK 72,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

SIIVET AS is registered as a limited company in Porsanger, Finnmark with organisation number 991172181. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon av film og video samt andre audiovisuelle produksjoner, og annet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −50,000
Equity
NOK 72,000
Est. value
NOK 3.4m

Financial health · 2024

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

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

Who owns SIIVET AS?

ANSTEIN MIKKELSEN
SIIVET AS
NOK 2.0m rev. · NOK −50,000 profit

SIIVET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIIVET AS

Who owns SIIVET AS?

ANSTEIN MIKKELSEN is the largest registered owner, with 100.0%.

What is the revenue of SIIVET AS?

SIIVET AS had revenue of NOK 2.0m in 2024.

Who is the general manager of SIIVET AS?

Anstein Mikkelsen is registered as general manager of SIIVET AS.

Where is SIIVET AS based?

SIIVET AS has its business address in Lakselv.

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.