BIZTRAC BETA
Other support activities to arts and performing arts

PORRIDGE AS

Org. no. 934744683 Limited company (AS) Nesodden Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 764,000
Operating profit NOK 763,000
Equity NOK 617,000
Incorporated 2024
Share capital NOK 30,000

PORRIDGE AS is registered as a limited company in Nesodden, Akershus with organisation number 934744683. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Teknisk rådgivning og konsulenttjenester rettet mot kultur og underholdningssektoren, herunder også utøvelse av musikalsk kunst, samt utvikling og investering i lignende selskaper innenfor samme eller andre bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 764,000 in revenue and NOK 763,000 in operating profit.

Key figures · 2024

Revenue
NOK 764,000
Operating profit
NOK 763,000
Equity
NOK 617,000
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns PORRIDGE AS?

RICHARD JOHN PEREIRA DE FREITAS
PORRIDGE AS
NOK 764,000 rev. · NOK 763,000 profit

PORRIDGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PORRIDGE AS

Who owns PORRIDGE AS?

RICHARD JOHN PEREIRA DE FREITAS is the largest registered owner, with 100.0%.

What is the revenue of PORRIDGE AS?

PORRIDGE AS had revenue of NOK 764,000 in 2024.

Who is the general manager of PORRIDGE AS?

Richard John Pereira De Freitas is registered as general manager of PORRIDGE AS.

Where is PORRIDGE AS based?

PORRIDGE AS has its business address in Nesoddtangen.

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.