BIZTRAC BETA
Motion picture, video and television programme production activities

GRAPE CAR MEDIA AS

Org. no. 925615854 Limited company (AS) Lørenskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 688,000
Operating profit NOK 107,000
Equity NOK 79,000
Incorporated 2020
Share capital NOK 30,000

GRAPE CAR MEDIA AS is registered as a limited company in Lørenskog, Akershus with organisation number 925615854. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og salg av film. Og annen produksjon til media samt tilhørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 688,000 in revenue and NOK 107,000 in operating profit.

Key figures · 2025

Revenue
NOK 688,000
Operating profit
NOK 107,000
Equity
NOK 79,000
Est. value
NOK 669,000

Financial health · 2025

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

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

Who owns GRAPE CAR MEDIA AS?

TOM PETTER HANSEN
GRAPE CAR MEDIA AS
NOK 688,000 rev. · NOK 107,000 profit

GRAPE CAR MEDIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRAPE CAR MEDIA AS

Who owns GRAPE CAR MEDIA AS?

TOM PETTER HANSEN is the largest registered owner, with 100.0%.

What is the revenue of GRAPE CAR MEDIA AS?

GRAPE CAR MEDIA AS had revenue of NOK 688,000 in 2025.

Who is the general manager of GRAPE CAR MEDIA AS?

Tom Petter Hansen is registered as general manager of GRAPE CAR MEDIA AS.

Where is GRAPE CAR MEDIA AS based?

GRAPE CAR MEDIA AS has its business address in Rasta.

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.