BIZTRAC BETA
Construction of residential and non-residential buildings

SKJÆRGÅRD EIENDOM AS

Org. no. 920262848 Limited company (AS) Lyngdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 414,000
Equity NOK 858,000
Incorporated 2017
Employees 6
Share capital NOK 30,000

SKJÆRGÅRD EIENDOM AS is registered as a limited company in Lyngdal, Agder with organisation number 920262848. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive innen bygg- og anleggsrelatert virksomhet, samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 414,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 414,000
Equity
NOK 858,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns SKJÆRGÅRD EIENDOM AS?

SKJÆRGÅRD EIENDOM HOLDING AS
SKJÆRGÅRD EIENDOM AS
NOK 10.1m rev. · NOK 414,000 profit

SKJÆRGÅRD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKJÆRGÅRD EIENDOM AS

Who owns SKJÆRGÅRD EIENDOM AS?

SKJÆRGÅRD EIENDOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SKJÆRGÅRD EIENDOM AS?

SKJÆRGÅRD EIENDOM AS had revenue of NOK 10.1m in 2024.

Who is the general manager of SKJÆRGÅRD EIENDOM AS?

Trond Vegard Nilsen is registered as general manager of SKJÆRGÅRD EIENDOM AS.

Where is SKJÆRGÅRD EIENDOM AS based?

SKJÆRGÅRD EIENDOM AS has its business address in Lyngdal.

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.