biztrac. BETA
COMPANY REGISTER PROFILE
915351069 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Event catering activities

WATAN CATERING AS

Org. no. 915351069 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 13.9m
Operating profit NOK 988,000
Equity NOK 2.5m
Incorporated 2015
Employees 44
Share capital NOK 30,000

WATAN CATERING AS is registered as a limited company in Oslo, Oslo with organisation number 915351069. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2015 and has 44 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Cateringvirksomhet, Nærings- og nytelsesmidler - produksjon, Selskapslokaler, Eiendomshandel og -utleie”. The most recent filed accounts, for the 2025 financial year, show NOK 13.9m in revenue and NOK 988,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.9m
▼ −4 %
Operating profit
NOK 988,000
▼ −50 %
Equity
NOK 2.5m
▲ +47 %
Est. value
NOK 5.8m

Financial health · 2025

Liquidity
4.08
Very good
Current assets ÷ current liabilities
Profitability
30.7%
Very good
Return on total assets
Solidity
76.7%
Very good
Equity as a share of total capital

Who owns WATAN CATERING AS?

WATAN CATERING AS
NOK 13.9m rev. · NOK 988,000 profit

WATAN CATERING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about WATAN CATERING AS

Who owns WATAN CATERING AS?

MPA HOLDNING AS is the largest registered owner, with 51.0%.

What is the revenue of WATAN CATERING AS?

WATAN CATERING AS had revenue of NOK 13.9m in 2025.

Who is the general manager of WATAN CATERING AS?

Muhammad Usman Parvaiz is registered as general manager of WATAN CATERING AS.

Where is WATAN CATERING AS based?

WATAN CATERING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.