BIZTRAC BETA
Construction of residential and non-residential buildings

SØRENSEN BYGG AS

Org. no. 915096239 Limited company (AS) Vestvågøy Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −54,000
Equity NOK 4,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

SØRENSEN BYGG AS is registered as a limited company in Vestvågøy, Nordland with organisation number 915096239. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring, vedlikehold og salg av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −54,000
Equity
NOK 4,000
Est. value
NOK 851,000

Financial health · 2025

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

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

Who owns SØRENSEN BYGG AS?

JIM STEVE SØRENSEN
SØRENSEN BYGG AS
NOK 2.5m rev. · NOK −54,000 profit

SØRENSEN BYGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRENSEN BYGG AS

Who owns SØRENSEN BYGG AS?

JIM STEVE SØRENSEN is the largest registered owner, with 53.3%.

What is the revenue of SØRENSEN BYGG AS?

SØRENSEN BYGG AS had revenue of NOK 2.5m in 2025.

Who is the general manager of SØRENSEN BYGG AS?

Jim Steve Sørensen is registered as general manager of SØRENSEN BYGG AS.

Where is SØRENSEN BYGG AS based?

SØRENSEN BYGG AS has its business address in Leknes.

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.