BIZTRAC BETA
Motion picture, video and television programme production activities

ANTIPODE FILMS AS

Org. no. 913449711 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 8.0m
Operating profit NOK 60,000
Equity NOK −63,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−63k kr).

ANTIPODE FILMS AS is registered as a limited company in Oslo, Oslo with organisation number 913449711. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 6 shares. The company's stated purpose is: “Produksjon av audiovisuelle verk for kino, TV og andre medier/arenaer. Tjenester og service innen, eller i forbindelse med ovennevnte.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.0m in revenue and NOK 60,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.0m
Operating profit
NOK 60,000
Equity
NOK −63,000
Est. value
NOK 263,000

Financial health · 2025

Liquidity
0.85
Weak
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 ANTIPODE FILMS AS?

FABIEN OLIVIER GREENBERG
ANTIPODE FILMS AS
NOK 8.0m rev. · NOK 60,000 profit

ANTIPODE FILMS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANTIPODE FILMS AS

Who owns ANTIPODE FILMS AS?

FABIEN OLIVIER GREENBERG is the largest registered owner, with 50.0%.

What is the revenue of ANTIPODE FILMS AS?

ANTIPODE FILMS AS had revenue of NOK 8.0m in 2025.

Where is ANTIPODE FILMS AS based?

ANTIPODE FILMS 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.