BIZTRAC BETA
Retail sale of watches and jewellery

GULLSMED K E SANDO AS

Org. no. 915693393 Limited company (AS) Tinn Incorporated 1969 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 241,000
Equity NOK 2.8m
Incorporated 1969
Employees 7
Share capital NOK 1.6m

GULLSMED K E SANDO AS is registered as a limited company in Tinn, Telemark with organisation number 915693393. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1969 and has 7 registered employees. Registered share capital is NOK 1.6m, divided into 1550 shares. The company's stated purpose is: “Gullsmedforretning og hva hermed står i forbindelse. Det skal også være anledning til å eie aksjer og andeler i andre selskaper. ”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 241,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 241,000
Equity
NOK 2.8m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns GULLSMED K E SANDO AS?

BERNT JØRGEN SANDO
GULLSMED K E SANDO AS
NOK 4.5m rev. · NOK 241,000 profit

GULLSMED K E SANDO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLSMED K E SANDO AS

Who owns GULLSMED K E SANDO AS?

BERNT JØRGEN SANDO is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED K E SANDO AS?

GULLSMED K E SANDO AS had revenue of NOK 4.5m in 2024.

Who is the general manager of GULLSMED K E SANDO AS?

Bernt Jørgen Sando is registered as general manager of GULLSMED K E SANDO AS.

Where is GULLSMED K E SANDO AS based?

GULLSMED K E SANDO AS has its business address in Rjukan.

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.