biztrac. BETA
COMPANY REGISTER PROFILE
936788793 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Motion picture, video and television programme production activities

APAT AS

Org. no. 936788793 Limited company (AS) Bergen Incorporated 2025 Active
Revenue 2025 NOK 128,000
Operating profit NOK 17,000
Equity NOK 55,000
Incorporated 2025
Share capital NOK 47,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-12-09.

APAT AS is registered as a limited company in Bergen, Vestland with organisation number 936788793. 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 47,000, divided into 47000 shares. The company's stated purpose is: “Produsere film, video og fjernsynsprogram, inkludert, men ikke begrenset til, ideutvikling, manusutvikling, opptak, redigering, postproduksjon og distribusjon av audiovisuelt innhold.”. The most recent filed accounts, for the 2025 financial year, show NOK 128,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 128,000
Operating profit
NOK 17,000
Equity
NOK 55,000
Est. value
NOK 131,000

Financial health · 2025

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

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

Who owns APAT AS?

APAT AS
NOK 128,000 rev. · NOK 17,000 profit

APAT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about APAT AS

Who owns APAT AS?

Elias Kleive is the largest registered owner, with 50.0%.

What is the revenue of APAT AS?

APAT AS had revenue of NOK 128,000 in 2025.

Where is APAT AS based?

APAT AS has its business address in Fyllingsdalen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.