biztrac. BETA
COMPANY REGISTER PROFILE
915591507 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

SANG TRAN AS

Org. no. 915591507 Limited company (AS) Gjøvik Incorporated 2015 Active
Revenue 2025 NOK 4.0m
Operating profit NOK 2.8m
Equity NOK 14.8m
Incorporated 2015
Share capital NOK 250,000

SANG TRAN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 915591507. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2015. Registered share capital is NOK 250,000, divided into 2500 shares. The company's stated purpose is: “Allmen helsetjeneste gjennom egen praksis og deltakelse i private helseforetak samt tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
▼ −15 %
Operating profit
NOK 2.8m
▲ +24 %
Equity
NOK 14.8m
▲ +13 %
Est. value
NOK 20.0m

Financial health · 2025

Liquidity
0.59
Weak
Current assets ÷ current liabilities
Profitability
13.0%
Good
Return on total assets
Solidity
68.6%
Very good
Equity as a share of total capital

Who owns SANG TRAN AS?

SANG TRAN AS
NOK 4.0m rev. · NOK 2.8m profit

SANG TRAN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SANG TRAN AS own?

SANG TRAN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SANG TRAN AS

Who owns SANG TRAN AS?

Sang Tran is the largest registered owner, with 100.0%.

What is the revenue of SANG TRAN AS?

SANG TRAN AS had revenue of NOK 4.0m in 2025.

Who is the general manager of SANG TRAN AS?

Sang Tran is registered as general manager of SANG TRAN AS.

Where is SANG TRAN AS based?

SANG TRAN AS has its business address in Gjøvik.

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.