BIZTRAC BETA
Construction of residential and non-residential buildings

SKOGSETH EIENDOM AS

Org. no. 989005618 Limited company (AS) Verdal Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −215,000
Equity NOK 15.9m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−215k kr).

SKOGSETH EIENDOM AS is registered as a limited company in Verdal, Trøndelag with organisation number 989005618. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg utvikling og utleie av fast eiendom og driftsmidler, samt erverve og selge aksjer og verdipapir eller på annen måte investere i andre selskap og eiendommer, og det som naturlig hører til dette.”.

Key figures · 2024

Operating profit
NOK −215,000
Equity
NOK 15.9m
Est. value
NOK 16.3m

Financial health · 2024

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

Who owns SKOGSETH EIENDOM AS?

JIM ROGER SKOGSETH
SKOGSETH EIENDOM AS
· NOK −215,000 profit

SKOGSETH EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKOGSETH EIENDOM AS own?

SKOGSETH EIENDOM AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about SKOGSETH EIENDOM AS

Who owns SKOGSETH EIENDOM AS?

JIM ROGER SKOGSETH is the largest registered owner, with 100.0%.

Who is the general manager of SKOGSETH EIENDOM AS?

Jim Roger Skogseth is registered as general manager of SKOGSETH EIENDOM AS.

Where is SKOGSETH EIENDOM AS based?

SKOGSETH EIENDOM AS has its business address in Verdal.

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.