BIZTRAC BETA
Industrial product and fashion design activities

SÁMI STORIES AS

Org. no. 919821833 Limited company (AS) Alta Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 148,000
Operating profit NOK −10,000
Equity NOK 167,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

SÁMI STORIES AS is registered as a limited company in Alta, Finnmark with organisation number 919821833. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Samisk design, salg av ulike produkter og tjenester innen design og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 148,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 148,000
Operating profit
NOK −10,000
Equity
NOK 167,000
Est. value
NOK 237,000

Financial health · 2025

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

Who owns SÁMI STORIES AS?

MARIE LOUISE SOMBY HÆTTA
SÁMI STORIES AS
NOK 148,000 rev. · NOK −10,000 profit

SÁMI STORIES AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SÁMI STORIES AS

Who owns SÁMI STORIES AS?

MARIE LOUISE SOMBY HÆTTA is the largest registered owner, with 37.7%.

What is the revenue of SÁMI STORIES AS?

SÁMI STORIES AS had revenue of NOK 148,000 in 2025.

Who is the general manager of SÁMI STORIES AS?

Marie Louise Somby Hætta is registered as general manager of SÁMI STORIES AS.

Where is SÁMI STORIES AS based?

SÁMI STORIES AS has its business address in Alta.

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.