BIZTRAC BETA
Restaurant activities

PARESA ELISENBERG AS

Org. no. 917518262 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 26.4m
Operating profit NOK 6.0m
Equity NOK 6.2m
Incorporated 2016
Employees 19
Share capital NOK 30,000

PARESA ELISENBERG AS is registered as a limited company in Oslo, Oslo with organisation number 917518262. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016 and has 19 registered employees. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Drift av og investering i bar- og restaurantvirksomhet, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.4m in revenue and NOK 6.0m in operating profit.

Key figures · 2024

Revenue
NOK 26.4m
Operating profit
NOK 6.0m
Equity
NOK 6.2m
Est. value
NOK 20.8m

Financial health · 2024

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.9%
Good
Equity as a share of total capital

Who owns PARESA ELISENBERG AS?

THAI MARKET OSLO AS
PARESA ELISENBERG AS
NOK 26.4m rev. · NOK 6.0m profit

PARESA ELISENBERG AS has 2 registered shareholders:

All shareholders and roles →

Group structure

PARESA ELISENBERG AS er morselskap for 1 datterselskap:

Frequently asked questions about PARESA ELISENBERG AS

Who owns PARESA ELISENBERG AS?

THAI MARKET OSLO AS is the largest registered owner, with 90.1%.

What is the revenue of PARESA ELISENBERG AS?

PARESA ELISENBERG AS had revenue of NOK 26.4m in 2024.

Who is the general manager of PARESA ELISENBERG AS?

Erik Pedersen is registered as general manager of PARESA ELISENBERG AS.

Where is PARESA ELISENBERG AS based?

PARESA ELISENBERG 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.