biztrac. BETA
COMPANY REGISTER PROFILE
928313174 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

AS SØRMEK EIENDOM AS

Org. no. 928313174 Limited company (AS) Lindesnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 818,000
Equity NOK 4.7m
Incorporated 2021
Share capital NOK 78,000

AS SØRMEK EIENDOM AS is registered as a limited company in Lindesnes, Agder with organisation number 928313174. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 78,000, divided into 1500 shares. The company's stated purpose is: “Eie og forvalte fast eiendom og annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 818,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▼ −2 %
Operating profit
NOK 818,000
▼ −11 %
Equity
NOK 4.7m
▲ +15 %
Est. value
NOK 5.2m

Financial health · 2025

Liquidity
2.58
Very good
Current assets ÷ current liabilities
Profitability
11.5%
Good
Return on total assets
Solidity
92.2%
Very good
Equity as a share of total capital

Who owns AS SØRMEK EIENDOM AS?

AS SØRMEK EIENDOM AS
NOK 1.2m rev. · NOK 818,000 profit

AS SØRMEK EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AS SØRMEK EIENDOM AS

Who owns AS SØRMEK EIENDOM AS?

VETÅS HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of AS SØRMEK EIENDOM AS?

AS SØRMEK EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of AS SØRMEK EIENDOM AS?

Kjell Ivar Erland is registered as general manager of AS SØRMEK EIENDOM AS.

Where is AS SØRMEK EIENDOM AS based?

AS SØRMEK EIENDOM AS has its business address in Lindesnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.