BIZTRAC BETA
Rental and operating of own or leased real estate

STRØKSNES UTLEIEBYGG AS

Org. no. 966384468 Limited company (AS) Sørfold Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 394,000
Operating profit NOK 74,000
Equity NOK 172,000
Incorporated 1993
Share capital NOK 106,000

STRØKSNES UTLEIEBYGG AS is registered as a limited company in Sørfold, Nordland with organisation number 966384468. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 106,000, divided into 76 shares. The company's stated purpose is: “Utleie av egen fast eiendom samt handel med fisk og skalldyr, og annen virksomhet som faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 394,000 in revenue and NOK 74,000 in operating profit.

Key figures · 2025

Revenue
NOK 394,000
Operating profit
NOK 74,000
Equity
NOK 172,000
Est. value
NOK 270,000

Financial health · 2025

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

Who owns STRØKSNES UTLEIEBYGG AS?

HERMANN SÆRSTEN VATNAN
STRØKSNES UTLEIEBYGG AS
NOK 394,000 rev. · NOK 74,000 profit

STRØKSNES UTLEIEBYGG AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about STRØKSNES UTLEIEBYGG AS

Who owns STRØKSNES UTLEIEBYGG AS?

HERMANN SÆRSTEN VATNAN is the largest registered owner, with 13.2%.

What is the revenue of STRØKSNES UTLEIEBYGG AS?

STRØKSNES UTLEIEBYGG AS had revenue of NOK 394,000 in 2025.

Who is the general manager of STRØKSNES UTLEIEBYGG AS?

Steinar Jarle Strand is registered as general manager of STRØKSNES UTLEIEBYGG AS.

Where is STRØKSNES UTLEIEBYGG AS based?

STRØKSNES UTLEIEBYGG AS has its business address in Engan.

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.