BIZTRAC BETA
Motion picture, video and television programme production activities

DAVÁS FILM AS

Org. no. 813834332 Limited company (AS) Kautokeino Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 605,000
Operating profit NOK 54,000
Equity NOK 10,000
Incorporated 2014
Share capital NOK 30,000

DAVÁS FILM AS is registered as a limited company in Kautokeino, Finnmark with organisation number 813834332. 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 1000 shares. The company's stated purpose is: “Produksjon og salg av Audio visuell produksjon, kunst, opplæring og produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 605,000 in revenue and NOK 54,000 in operating profit.

Key figures · 2024

Revenue
NOK 605,000
Operating profit
NOK 54,000
Equity
NOK 10,000
Est. value
NOK 326,000

Financial health · 2024

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

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

Who owns DAVÁS FILM AS?

KEN-ARE MATHISSEN BONGO
DAVÁS FILM AS
NOK 605,000 rev. · NOK 54,000 profit

DAVÁS FILM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAVÁS FILM AS

Who owns DAVÁS FILM AS?

KEN-ARE MATHISSEN BONGO is the largest registered owner, with 100.0%.

What is the revenue of DAVÁS FILM AS?

DAVÁS FILM AS had revenue of NOK 605,000 in 2024.

Who is the general manager of DAVÁS FILM AS?

Ken-Are Mathissen Bongo is registered as general manager of DAVÁS FILM AS.

Where is DAVÁS FILM AS based?

DAVÁS FILM AS has its business address in Kautokeino.

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.