BIZTRAC BETA
Motion picture, video and television programme production activities

FOLKEFIENDER AS

Org. no. 819002622 Limited company (AS) Nordre Follo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 15,000
Operating profit NOK −57
Equity NOK −20,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−20k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−57 kr).

FOLKEFIENDER AS is registered as a limited company in Nordre Follo, Akershus with organisation number 819002622. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon av fiksjonsfilm, dokumentar og reklame. Med hertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 15,000 in revenue and NOK −57 in operating profit.

Key figures · 2025

Revenue
NOK 15,000
Operating profit
NOK −57
Equity
NOK −20,000

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-832.9%
Weak
Equity as a share of total capital

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

Who owns FOLKEFIENDER AS?

HENRY KRAGEBØL NORVALLS
FOLKEFIENDER AS
NOK 15,000 rev. · NOK −57 profit

FOLKEFIENDER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOLKEFIENDER AS

Who owns FOLKEFIENDER AS?

HENRY KRAGEBØL NORVALLS is the largest registered owner, with 33.3%.

What is the revenue of FOLKEFIENDER AS?

FOLKEFIENDER AS had revenue of NOK 15,000 in 2025.

Where is FOLKEFIENDER AS based?

FOLKEFIENDER AS has its business address in Sofiemyr.

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.