BIZTRAC BETA
Public relations and communication activities

PATRIKSSON COMMUNICATION AS

Org. no. 918347933 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 16.7m
Operating profit NOK 1.3m
Equity NOK 3.9m
Incorporated 2016
Employees 9
Share capital NOK 52,000

PATRIKSSON COMMUNICATION AS is registered as a limited company in Oslo, Oslo with organisation number 918347933. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2016 and has 9 registered employees. Registered share capital is NOK 52,000, divided into 1000 shares. The company's stated purpose is: “Virksomhet innen kommunikasjon og PR tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.7m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 16.7m
Operating profit
NOK 1.3m
Equity
NOK 3.9m
Est. value
NOK 8.5m

Financial health · 2024

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

Who owns PATRIKSSON COMMUNICATION AS?

PATRIKSSON COMMUNICATION AB
PATRIKSSON COMMUNICATION AS
NOK 16.7m rev. · NOK 1.3m profit

PATRIKSSON COMMUNICATION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PATRIKSSON COMMUNICATION AS

Who owns PATRIKSSON COMMUNICATION AS?

PATRIKSSON COMMUNICATION AB is the largest registered owner, with 100.0%.

What is the revenue of PATRIKSSON COMMUNICATION AS?

PATRIKSSON COMMUNICATION AS had revenue of NOK 16.7m in 2024.

Who is the general manager of PATRIKSSON COMMUNICATION AS?

Jesper Bo Mårten Kling is registered as general manager of PATRIKSSON COMMUNICATION AS.

Where is PATRIKSSON COMMUNICATION AS based?

PATRIKSSON COMMUNICATION AS has its business address in Oslo.

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.