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

WERGELAND PROPERTY AS

Org. no. 932514389 Limited company (AS) Gulen Incorporated 2023 Active
Revenue 2025 NOK 6.8m
Operating profit NOK 6.2m
Equity NOK 7.5m
Incorporated 2023
Share capital NOK 30,000

WERGELAND PROPERTY AS is registered as a limited company in Gulen, Vestland with organisation number 932514389. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og drive eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK 6.2m in operating profit.

Former names: AMAGL INVEST 27 AS

Key figures · 2025

Revenue
NOK 6.8m
▼ −8 %
Operating profit
NOK 6.2m
▼ −15 %
Equity
NOK 7.5m
▲ +44 %
Est. value
NOK 17.8m

Financial health · 2025

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
33.0%
Very good
Return on total assets
Solidity
39.3%
Good
Equity as a share of total capital

Who owns WERGELAND PROPERTY AS?

WERGELAND PROPERTY AS
NOK 6.8m rev. · NOK 6.2m profit

WERGELAND PROPERTY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WERGELAND PROPERTY AS

Who owns WERGELAND PROPERTY AS?

WERGELAND PROPERTY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of WERGELAND PROPERTY AS?

WERGELAND PROPERTY AS had revenue of NOK 6.8m in 2025.

Who is the general manager of WERGELAND PROPERTY AS?

Irene Perly Kjelby Wergeland is registered as general manager of WERGELAND PROPERTY AS.

Where is WERGELAND PROPERTY AS based?

WERGELAND PROPERTY AS has its business address in Dalsøyra.

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.