BIZTRAC BETA
Motion picture, video and television programme production activities

PILLARGURI PRODUCTIONS AS

Org. no. 934099702 Limited company (AS) Sel Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 50,000
Operating profit NOK −3,000
Equity NOK 22,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

PILLARGURI PRODUCTIONS AS is registered as a limited company in Sel, Innlandet with organisation number 934099702. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon av film, bilde og markedsføringsmateriell til ulike formål. Dronefilming.”. The most recent filed accounts, for the 2024 financial year, show NOK 50,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 50,000
Operating profit
NOK −3,000
Equity
NOK 22,000
Est. value
NOK 94,000

Financial health · 2024

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

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

Who owns PILLARGURI PRODUCTIONS AS?

ØYSTEIN THO
PILLARGURI PRODUCTIONS AS
NOK 50,000 rev. · NOK −3,000 profit

PILLARGURI PRODUCTIONS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PILLARGURI PRODUCTIONS AS

Who owns PILLARGURI PRODUCTIONS AS?

ØYSTEIN THO is the largest registered owner, with 50.0%.

What is the revenue of PILLARGURI PRODUCTIONS AS?

PILLARGURI PRODUCTIONS AS had revenue of NOK 50,000 in 2024.

Where is PILLARGURI PRODUCTIONS AS based?

PILLARGURI PRODUCTIONS AS has its business address in Otta.

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.