BIZTRAC BETA
Activities of excursion and event organisers

PRO SERVICE OSLO AS

Org. no. 819751722 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 11,000
Equity NOK 8,000
Incorporated 2017
Share capital NOK 30,000

PRO SERVICE OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 819751722. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg, service og utleie av produkter relatert til utelivsbransjen/eventbransjen. Utleie av arbeidskraft og alt hva hermed er i forbindelse og deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 11,000
Equity
NOK 8,000
Est. value
NOK 59,000

Financial health · 2025

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

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

Who owns PRO SERVICE OSLO AS?

NICO DEKKE
PRO SERVICE OSLO AS
NOK 3.6m rev. · NOK 11,000 profit

PRO SERVICE OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PRO SERVICE OSLO AS

Who owns PRO SERVICE OSLO AS?

NICO DEKKE is the largest registered owner, with 100.0%.

What is the revenue of PRO SERVICE OSLO AS?

PRO SERVICE OSLO AS had revenue of NOK 3.6m in 2025.

Who is the general manager of PRO SERVICE OSLO AS?

Nico Dekke is registered as general manager of PRO SERVICE OSLO AS.

Where is PRO SERVICE OSLO AS based?

PRO SERVICE 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.