BIZTRAC BETA
Motion picture, video and television programme production activities

PINPOINT AS

Org. no. 935908000 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 2.5m
Equity NOK 2.0m
Incorporated 2025
Share capital NOK 30,000

PINPOINT AS is registered as a limited company in Oslo, Oslo with organisation number 935908000. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen filmproduksjon og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
Operating profit
NOK 2.5m
Equity
NOK 2.0m
Est. value
NOK 9.4m

Financial health · 2025

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

Who owns PINPOINT AS?

MEGALO MEDIA AS
PINPOINT AS
NOK 4.9m rev. · NOK 2.5m profit

PINPOINT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PINPOINT AS own?

PINPOINT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PINPOINT AS

Who owns PINPOINT AS?

MEGALO MEDIA AS is the largest registered owner, with 50.0%.

What is the revenue of PINPOINT AS?

PINPOINT AS had revenue of NOK 4.9m in 2025.

Who is the general manager of PINPOINT AS?

Sindre Wiig Nordby is registered as general manager of PINPOINT AS.

Where is PINPOINT AS based?

PINPOINT AS has its business address in Oslo.

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.