BIZTRAC BETA
Rental and operating of own or leased real estate

SALANGEN FORRETNINGSBYGG AS

Org. no. 942842511 Limited company (AS) Tromsø Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 5.9m
Operating profit NOK 1.4m
Equity NOK 1.1m
Incorporated 1987
Share capital NOK 100,000

SALANGEN FORRETNINGSBYGG AS is registered as a limited company in Tromsø, Troms with organisation number 942842511. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av forretningsbygg, konsulentvirksomhet innefor bygg og shipping, samt kjøp og salg av aksjer og andre verdipapirer. Selskapet skal også kunne delta i andre selskap med beslektet virksomhet, samt delta i annen type næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 5.9m
Operating profit
NOK 1.4m
Equity
NOK 1.1m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns SALANGEN FORRETNINGSBYGG AS?

EGIL LYNUM
SALANGEN FORRETNINGSBYGG AS
NOK 5.9m rev. · NOK 1.4m profit

SALANGEN FORRETNINGSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALANGEN FORRETNINGSBYGG AS

Who owns SALANGEN FORRETNINGSBYGG AS?

EGIL LYNUM is the largest registered owner, with 100.0%.

What is the revenue of SALANGEN FORRETNINGSBYGG AS?

SALANGEN FORRETNINGSBYGG AS had revenue of NOK 5.9m in 2024.

Where is SALANGEN FORRETNINGSBYGG AS based?

SALANGEN FORRETNINGSBYGG AS has its business address in Tromsø.

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.