BIZTRAC BETA
Site preparation

NES SERVICE AS

Org. no. 930481017 Limited company (AS) Lyngdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 105,000
Operating profit NOK 50,000
Equity NOK 163,000
Incorporated 2022
Share capital NOK 30,000

NES SERVICE AS is registered as a limited company in Lyngdal, Agder with organisation number 930481017. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal selge tjenester og varer innen utleie av arbeidskraft. - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 105,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2024

Revenue
NOK 105,000
Operating profit
NOK 50,000
Equity
NOK 163,000
Est. value
NOK 225,000

Financial health · 2024

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

Who owns NES SERVICE AS?

DIDRIK NES
NES SERVICE AS
NOK 105,000 rev. · NOK 50,000 profit

NES SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NES SERVICE AS own?

NES SERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NES SERVICE AS

Who owns NES SERVICE AS?

DIDRIK NES is the largest registered owner, with 100.0%.

What is the revenue of NES SERVICE AS?

NES SERVICE AS had revenue of NOK 105,000 in 2024.

Who is the general manager of NES SERVICE AS?

Didrik Nes is registered as general manager of NES SERVICE AS.

Where is NES SERVICE AS based?

NES SERVICE 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.