BIZTRAC BETA
Business and other management consultancy activities

TRIGGER OSLO AS

Org. no. 914345561 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 63.6m
Operating profit NOK 3.0m
Equity NOK 6.4m
Incorporated 2014
Employees 40
Share capital NOK 40,000

TRIGGER OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 914345561. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014 and has 40 registered employees. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Rådgivning innen omdømmearbeid, PR og markedskommunikasjon, samt produksjon av informasjons- og markedsmateriell og alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 63.6m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 63.6m
Operating profit
NOK 3.0m
Equity
NOK 6.4m
Est. value
NOK 17.9m

Financial health · 2024

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.8%
Good
Equity as a share of total capital

Who owns TRIGGER OSLO AS?

TRIGGER WORLD AS
TRIGGER OSLO AS
NOK 63.6m rev. · NOK 3.0m profit

TRIGGER OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRIGGER OSLO AS

Who owns TRIGGER OSLO AS?

TRIGGER WORLD AS is the largest registered owner, with 100.0%.

What is the revenue of TRIGGER OSLO AS?

TRIGGER OSLO AS had revenue of NOK 63.6m in 2024.

Who is the general manager of TRIGGER OSLO AS?

Bente Kvam Kristoffersen is registered as general manager of TRIGGER OSLO AS.

Where is TRIGGER OSLO AS based?

TRIGGER OSLO 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.