BIZTRAC BETA
Other specialised construction activities n.e.c.

SALTVIND AS

Org. no. 932393107 Limited company (AS) Loppa Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 523,000
Equity NOK 46,000
Incorporated 2023
Employees 6
Share capital NOK 100,000

SALTVIND AS is registered as a limited company in Loppa, Finnmark with organisation number 932393107. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvendig boligssikring ift taksikring som takstiger, brannstiger, fasadestiger, adkomststiger med mer, videre bytting av beslag, piper og lyrer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 523,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 523,000
Equity
NOK 46,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SALTVIND AS?

RUBEN SOGOOD ELVEBAKKEN
SALTVIND AS
NOK 3.2m rev. · NOK 523,000 profit

SALTVIND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALTVIND AS

Who owns SALTVIND AS?

RUBEN SOGOOD ELVEBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of SALTVIND AS?

SALTVIND AS had revenue of NOK 3.2m in 2025.

Who is the general manager of SALTVIND AS?

Ruben Sogood Elvebakken is registered as general manager of SALTVIND AS.

Where is SALTVIND AS based?

SALTVIND AS has its business address in Bergsfjord.

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.