BIZTRAC BETA
Repair and maintenance of machinery

SØRVEST KRAN & REP AS

Org. no. 921705298 Limited company (AS) Time Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 23.8m
Operating profit NOK 3.1m
Equity NOK 2.3m
Incorporated 2018
Employees 9
Share capital NOK 50,000

SØRVEST KRAN & REP AS is registered as a limited company in Time, Rogaland with organisation number 921705298. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2018 and has 9 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Salg, kjøp, reparasjon, kontroll, vedlikehold og montasje av kraner, maskiner og utstyr samt hva som heri står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.8m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 23.8m
Operating profit
NOK 3.1m
Equity
NOK 2.3m
Est. value
NOK 11.6m

Financial health · 2024

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

Who owns SØRVEST KRAN & REP AS?

TORBJØRN SKOGLAND OBRESTAD
SØRVEST KRAN & REP AS
NOK 23.8m rev. · NOK 3.1m profit

SØRVEST KRAN & REP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRVEST KRAN & REP AS

Who owns SØRVEST KRAN & REP AS?

TORBJØRN SKOGLAND OBRESTAD is the largest registered owner, with 50.0%.

What is the revenue of SØRVEST KRAN & REP AS?

SØRVEST KRAN & REP AS had revenue of NOK 23.8m in 2024.

Who is the general manager of SØRVEST KRAN & REP AS?

Torbjørn Skogland Obrestad is registered as general manager of SØRVEST KRAN & REP AS.

Where is SØRVEST KRAN & REP AS based?

SØRVEST KRAN & REP AS has its business address in Bryne.

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.