BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

SEWE UTLEIE AS

Org. no. 932586479 Limited company (AS) Surnadal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 693,000
Operating profit NOK 141,000
Equity NOK 101,000
Incorporated 2023
Share capital NOK 100,000

SEWE UTLEIE AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 932586479. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og drive utleie av driftsmidler og bygninger, og alt står i forbindelse hermed, herunder å delta andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 693,000 in revenue and NOK 141,000 in operating profit.

Key figures · 2025

Revenue
NOK 693,000
Operating profit
NOK 141,000
Equity
NOK 101,000
Est. value
NOK 487,000

Financial health · 2025

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

Who owns SEWE UTLEIE AS?

WEKRE INVEST AS
SEWE UTLEIE AS
NOK 693,000 rev. · NOK 141,000 profit

SEWE UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEWE UTLEIE AS

Who owns SEWE UTLEIE AS?

WEKRE INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of SEWE UTLEIE AS?

SEWE UTLEIE AS had revenue of NOK 693,000 in 2025.

Who is the general manager of SEWE UTLEIE AS?

Øyvind Wekre is registered as general manager of SEWE UTLEIE AS.

Where is SEWE UTLEIE AS based?

SEWE UTLEIE AS has its business address in Surnadal.

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.