BIZTRAC BETA
Other education activities

ERSVIKA SAMISKE SIIDA AS

Org. no. 917731551 Limited company (AS) Bodø Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 480,000
Equity NOK 249,000
Incorporated 2016
Share capital NOK 30,000

ERSVIKA SAMISKE SIIDA AS is registered as a limited company in Bodø, Nordland with organisation number 917731551. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kulturell og pedagogisk undervisning i samisk og nordisk kultur, avlastningshjem og feriekoloni, og annet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 480,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 480,000
Equity
NOK 249,000
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns ERSVIKA SAMISKE SIIDA AS?

MARIA THERESE GYLSETH HAUGE
ERSVIKA SAMISKE SIIDA AS
NOK 3.7m rev. · NOK 480,000 profit

ERSVIKA SAMISKE SIIDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERSVIKA SAMISKE SIIDA AS

Who owns ERSVIKA SAMISKE SIIDA AS?

MARIA THERESE GYLSETH HAUGE is the largest registered owner, with 100.0%.

What is the revenue of ERSVIKA SAMISKE SIIDA AS?

ERSVIKA SAMISKE SIIDA AS had revenue of NOK 3.7m in 2025.

Who is the general manager of ERSVIKA SAMISKE SIIDA AS?

Maria Therese Gylseth Hauge is registered as general manager of ERSVIKA SAMISKE SIIDA AS.

Where is ERSVIKA SAMISKE SIIDA AS based?

ERSVIKA SAMISKE SIIDA AS has its business address in Tverlandet.

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.