BIZTRAC BETA
Public relations and communication activities

TOMMY ELLINGSEN AS

Org. no. 933815250 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 137,000
Operating profit NOK 79,000
Equity NOK 91,000
Incorporated 2024
Share capital NOK 30,000

TOMMY ELLINGSEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 933815250. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Konsulenttjenester innen PR, strategi og markedsføring, samt produksjon av både redaksjonelt og kommersielt innhold.”. The most recent filed accounts, for the 2024 financial year, show NOK 137,000 in revenue and NOK 79,000 in operating profit.

Key figures · 2024

Revenue
NOK 137,000
Operating profit
NOK 79,000
Equity
NOK 91,000
Est. value
NOK 310,000

Financial health · 2024

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

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

Who owns TOMMY ELLINGSEN AS?

INGRID VOLL JOAKIMSEN
TOMMY ELLINGSEN AS
NOK 137,000 rev. · NOK 79,000 profit

TOMMY ELLINGSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOMMY ELLINGSEN AS

Who owns TOMMY ELLINGSEN AS?

INGRID VOLL JOAKIMSEN is the largest registered owner, with 50.0%.

What is the revenue of TOMMY ELLINGSEN AS?

TOMMY ELLINGSEN AS had revenue of NOK 137,000 in 2024.

Who is the general manager of TOMMY ELLINGSEN AS?

Ingrid Voll Joakimsen is registered as general manager of TOMMY ELLINGSEN AS.

Where is TOMMY ELLINGSEN AS based?

TOMMY ELLINGSEN AS has its business address in Stavanger.

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.