BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

SPAR TYSNES AS

Org. no. 986912878 Limited company (AS) Tysnes Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 57.0m
Operating profit NOK 2.2m
Equity NOK 14.1m
Incorporated 2004
Employees 26
Share capital NOK 251,000

SPAR TYSNES AS is registered as a limited company in Tysnes, Vestland with organisation number 986912878. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2004 and has 26 registered employees. Registered share capital is NOK 251,000, divided into 250 shares. The company's stated purpose is: “Salg av handelsvarer og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 57.0m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 57.0m
Operating profit
NOK 2.2m
Equity
NOK 14.1m
Est. value
NOK 17.2m

Financial health · 2024

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

Who owns SPAR TYSNES AS?

KJERSTI BREKKE
SPAR TYSNES AS
NOK 57.0m rev. · NOK 2.2m profit

SPAR TYSNES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPAR TYSNES AS own?

SPAR TYSNES AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SPAR TYSNES AS

Who owns SPAR TYSNES AS?

KJERSTI BREKKE is the largest registered owner, with 100.0%.

What is the revenue of SPAR TYSNES AS?

SPAR TYSNES AS had revenue of NOK 57.0m in 2024.

Who is the general manager of SPAR TYSNES AS?

Kjersti Brekke is registered as general manager of SPAR TYSNES AS.

Where is SPAR TYSNES AS based?

SPAR TYSNES AS has its business address in Tysnes.

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.