biztrac. BETA
COMPANY REGISTER PROFILE
980833305 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

LYNGUTBYGGEREN AS

Org. no. 980833305 Limited company (AS) Lyngdal Incorporated 1999 Active
Ownership graph ↗
Operating profit NOK −180,000
Equity NOK 813,000
Incorporated 1999
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−180k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LYNGUTBYGGEREN AS is registered as a limited company in Lyngdal, Agder with organisation number 980833305. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppkjøp og utbygging av prosjekter, eie fast eiendom og eventuelt investere i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −180,000
▲ +40 %
Equity
NOK 813,000
▲ +70 %
Est. value
NOK 742,000

Financial health · 2025

Liquidity
11.69
Very good
Current assets ÷ current liabilities
Profitability
-2.3%
Not satisfactory
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

Who owns LYNGUTBYGGEREN AS?

LYNGUTBYGGEREN AS
· NOK −180,000 profit

LYNGUTBYGGEREN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LYNGUTBYGGEREN AS er morselskap for 7 datterselskaper:

Frequently asked questions about LYNGUTBYGGEREN AS

Who owns LYNGUTBYGGEREN AS?

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

Who is the general manager of LYNGUTBYGGEREN AS?

Ivar Henning Persson is registered as general manager of LYNGUTBYGGEREN AS.

Where is LYNGUTBYGGEREN AS based?

LYNGUTBYGGEREN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.