biztrac. BETA
COMPANY REGISTER PROFILE
990028265 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Holiday and other short-stay accommodation

SØRHEIM BRYGGE AS

Org. no. 990028265 Limited company (AS) Lyngen Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 226,000
Equity NOK 6.9m
Incorporated 2006
Share capital NOK 7.3m

SØRHEIM BRYGGE AS is registered as a limited company in Lyngen, Troms with organisation number 990028265. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2006. Registered share capital is NOK 7.3m, divided into 73000 shares. The company's stated purpose is: “Kjøp/salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 226,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
▼ −49 %
Operating profit
NOK 226,000
▼ −86 %
Equity
NOK 6.9m
▼ −3 %
Est. value
NOK 5.1m

Financial health · 2025

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
1.7%
Weak
Return on total assets
Solidity
49.6%
Very good
Equity as a share of total capital

Who owns SØRHEIM BRYGGE AS?

SØRHEIM BRYGGE AS
NOK 2.2m rev. · NOK 226,000 profit

SØRHEIM BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SØRHEIM BRYGGE AS own?

SØRHEIM BRYGGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØRHEIM BRYGGE AS

Who owns SØRHEIM BRYGGE AS?

S-E HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SØRHEIM BRYGGE AS?

SØRHEIM BRYGGE AS had revenue of NOK 2.2m in 2025.

Who is the general manager of SØRHEIM BRYGGE AS?

Stein-Erik Eliassen is registered as general manager of SØRHEIM BRYGGE AS.

Where is SØRHEIM BRYGGE AS based?

SØRHEIM BRYGGE AS has its business address in Lyngseidet.

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.