biztrac. BETA
COMPANY REGISTER PROFILE
914739411 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

LL SØRCO AS

Org. no. 914739411 Limited company (AS) Surnadal Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −117,000
Equity NOK 452.1m
Incorporated 2014
Share capital NOK 15.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−117k kr).

LL SØRCO AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 914739411. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 15.0m, divided into 5000 shares. The company's stated purpose is: “Erverv og oppføring av fast eiendom, samt gjennom eierinteresser å delta i andre selskap som har eiendomsdrift eller annen forretningsvirksomhet som formål.”.

Former names: BROTORVET HOLDING AS

Key figures · 2025

Operating profit
NOK −117,000
▲ +63 %
Equity
NOK 452.1m
▲ +6 %
Est. value
NOK 404.1m

Financial health · 2025

Liquidity
4.26
Very good
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns LL SØRCO AS?

LL SØRCO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LL SØRCO AS own?

LL SØRCO AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

LL SØRCO AS er morselskap for 1 datterselskap:

Frequently asked questions about LL SØRCO AS

Who owns LL SØRCO AS?

SØRCO KJØPESENTER AS is the largest registered owner, with 50.0%.

Who is the general manager of LL SØRCO AS?

Olav Smevoll is registered as general manager of LL SØRCO AS.

Where is LL SØRCO AS based?

LL SØRCO AS has its business address in Surnadal.

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.