BIZTRAC BETA
Rental and operating of own or leased real estate

VERKSGÅRDEN AS

Org. no. 979640188 Limited company (AS) Strand Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 742,000
Equity NOK 9.3m
Incorporated 1998
Share capital NOK 1.5m

VERKSGÅRDEN AS is registered as a limited company in Strand, Rogaland with organisation number 979640188. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Kjøp, salg og utvikling/utbygging av tomter, boliger og forretnings- eiendommer, samt investering i andre selskaper, samt generell næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 742,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 742,000
Equity
NOK 9.3m
Est. value
NOK 7.8m

Financial health · 2025

Liquidity
5.07
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
64.6%
Very good
Equity as a share of total capital

Who owns VERKSGÅRDEN AS?

REKELLY AS
VERKSGÅRDEN AS
NOK 1.4m rev. · NOK 742,000 profit

VERKSGÅRDEN AS has 4 registered shareholders:

All shareholders and roles →

Which companies does VERKSGÅRDEN AS own?

VERKSGÅRDEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VERKSGÅRDEN AS

Who owns VERKSGÅRDEN AS?

REKELLY AS is the largest registered owner, with 33.3%.

What is the revenue of VERKSGÅRDEN AS?

VERKSGÅRDEN AS had revenue of NOK 1.4m in 2025.

Who is the general manager of VERKSGÅRDEN AS?

Erling Magnar Tvedt is registered as general manager of VERKSGÅRDEN AS.

Where is VERKSGÅRDEN AS based?

VERKSGÅRDEN AS has its business address in Jørpeland.

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.