BIZTRAC BETA
Motion picture, video and television programme production activities

FEBER PRAT AS

Org. no. 931167901 Limited company (AS) Alta Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 44,000
Operating profit NOK 35,000
Equity NOK 69,000
Incorporated 2023
Share capital NOK 40,000

FEBER PRAT AS is registered as a limited company in Alta, Finnmark with organisation number 931167901. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Tilby tjenester innenfor kommunikasjon, kommentatoroppdrag på TV-sendinger, radiosendinger og andre plattformer, i tillegg til andre media- og konsulentoppdrag som naturlig sammenfaller med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 44,000 in revenue and NOK 35,000 in operating profit.

Key figures · 2025

Revenue
NOK 44,000
Operating profit
NOK 35,000
Equity
NOK 69,000
Est. value
NOK 154,000

Financial health · 2025

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

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

Who owns FEBER PRAT AS?

FEBER HOLDING AS
FEBER PRAT AS
NOK 44,000 rev. · NOK 35,000 profit

FEBER PRAT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FEBER PRAT AS er morselskap for 2 datterselskaper:

Frequently asked questions about FEBER PRAT AS

Who owns FEBER PRAT AS?

FEBER HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FEBER PRAT AS?

FEBER PRAT AS had revenue of NOK 44,000 in 2025.

Where is FEBER PRAT AS based?

FEBER PRAT AS has its business address in Alta.

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.