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

TINE HEDSTEN AS

Org. no. 915577997 Limited company (AS) Stjørdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 89.3m
Operating profit NOK 1.5m
Equity NOK 4.7m
Incorporated 2015
Employees 20
Share capital NOK 500,000

TINE HEDSTEN AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 915577997. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2015 and has 20 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 89.3m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 89.3m
Operating profit
NOK 1.5m
Equity
NOK 4.7m
Est. value
NOK 8.2m

Financial health · 2025

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.3%
Good
Equity as a share of total capital

Who owns TINE HEDSTEN AS?

TINE HEDSTEN
TINE HEDSTEN AS
NOK 89.3m rev. · NOK 1.5m profit

TINE HEDSTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TINE HEDSTEN AS

Who owns TINE HEDSTEN AS?

TINE HEDSTEN is the largest registered owner, with 100.0%.

What is the revenue of TINE HEDSTEN AS?

TINE HEDSTEN AS had revenue of NOK 89.3m in 2025.

Who is the general manager of TINE HEDSTEN AS?

Tine Hedsten is registered as general manager of TINE HEDSTEN AS.

Where is TINE HEDSTEN AS based?

TINE HEDSTEN AS has its business address in Stjørdal.

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.