BIZTRAC BETA
Rental and operating of own or leased real estate

HARSVIK BRYGGE AS

Org. no. 917878706 Limited company (AS) Åfjord Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 110,000
Operating profit NOK 16,000
Equity NOK 578,000
Incorporated 2016
Share capital NOK 100,000

HARSVIK BRYGGE AS is registered as a limited company in Åfjord, Trøndelag with organisation number 917878706. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Selskapet kan engasjere seg i annen virksomhet ved kjøp og salg av aksjer og verdipapirer, samt andre tiltak beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 110,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 110,000
Operating profit
NOK 16,000
Equity
NOK 578,000
Est. value
NOK 424,000

Financial health · 2025

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

Who owns HARSVIK BRYGGE AS?

STURLA GABRIELSEN
HARSVIK BRYGGE AS
NOK 110,000 rev. · NOK 16,000 profit

HARSVIK BRYGGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HARSVIK BRYGGE AS

Who owns HARSVIK BRYGGE AS?

STURLA GABRIELSEN is the largest registered owner, with 50.0%.

What is the revenue of HARSVIK BRYGGE AS?

HARSVIK BRYGGE AS had revenue of NOK 110,000 in 2025.

Who is the general manager of HARSVIK BRYGGE AS?

Trond Erling Navelsaker Slind is registered as general manager of HARSVIK BRYGGE AS.

Where is HARSVIK BRYGGE AS based?

HARSVIK BRYGGE AS has its business address in Stokkøy.

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.