BIZTRAC BETA
General medical practice activities

STORBYEN LEGESENTER AS

Org. no. 981622081 Limited company (AS) Sarpsborg Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 259,000
Equity NOK 499,000
Incorporated 2000
Share capital NOK 100,000

STORBYEN LEGESENTER AS is registered as a limited company in Sarpsborg, Østfold with organisation number 981622081. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 3000 shares. The company's stated purpose is: “Å drive legevirksomhet, kjøp og salg samt delta i annen virksomhet ved tegning av aksjer eller på annen måte samt annet som naturlig hører herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 259,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 259,000
Equity
NOK 499,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns STORBYEN LEGESENTER AS?

CEREN TAMGULER BARRETO RIOS
STORBYEN LEGESENTER AS
NOK 2.7m rev. · NOK 259,000 profit

STORBYEN LEGESENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORBYEN LEGESENTER AS

Who owns STORBYEN LEGESENTER AS?

CEREN TAMGULER BARRETO RIOS is the largest registered owner, with 33.3%.

What is the revenue of STORBYEN LEGESENTER AS?

STORBYEN LEGESENTER AS had revenue of NOK 2.7m in 2025.

Who is the general manager of STORBYEN LEGESENTER AS?

Usama Abid is registered as general manager of STORBYEN LEGESENTER AS.

Where is STORBYEN LEGESENTER AS based?

STORBYEN LEGESENTER AS has its business address in Sarpsborg.

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.