biztrac. BETA
COMPANY REGISTER PROFILE
991754512 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Retail sale of textiles

UBR SCANDINAVIA AS

Org. no. 991754512 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 139.1m
Operating profit NOK 18.7m
Equity NOK 40.7m
Incorporated 2007
Employees 16
Share capital NOK 124,000

UBR SCANDINAVIA AS is registered as a limited company in Oslo, Oslo with organisation number 991754512. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2007 and has 16 registered employees. Registered share capital is NOK 124,000, divided into 1236670 shares. The company's stated purpose is: “Investere i fast eiendom og verdipapirer samt drive konsulentvirksomhet, produktutvikling og varehandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 139.1m in revenue and NOK 18.7m in operating profit.

Former names: QA PROPERTIES AS, UBER AS

Key figures · 2025

Revenue
NOK 139.1m
▲ +16 %
Operating profit
NOK 18.7m
▲ +12 %
Equity
NOK 40.7m
▲ +48 %
Est. value
NOK 80.2m

Financial health · 2025

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

Who owns UBR SCANDINAVIA AS?

UBR SCANDINAVIA AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about UBR SCANDINAVIA AS

Who owns UBR SCANDINAVIA AS?

SCANDINAVIAN SUPREME AS is the largest registered owner, with 82.2%.

What is the revenue of UBR SCANDINAVIA AS?

UBR SCANDINAVIA AS had revenue of NOK 139.1m in 2025.

Who is the general manager of UBR SCANDINAVIA AS?

Dag Even Hovda Tresselt is registered as general manager of UBR SCANDINAVIA AS.

Where is UBR SCANDINAVIA AS based?

UBR SCANDINAVIA 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.