BIZTRAC BETA
COMPANY REGISTER PROFILE
932375745 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Site preparation

JL ANLEGG AS

Org. no. 932375745 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 14,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

JL ANLEGG AS is registered as a limited company in Bergen, Vestland with organisation number 932375745. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vegarbeid, bygg og anleggsarbeid og andre produkter/tjenester som naturlig hører til dette.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −2 %
Equity
NOK 14,000
▼ −38 %
Est. value
NOK 14,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JL ANLEGG AS?

JL ANLEGG AS
· NOK −8,000 profit

JL ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JL ANLEGG AS

Who owns JL ANLEGG AS?

JONAS SANDNES LINDSTAD is the largest registered owner, with 100.0%.

Where is JL ANLEGG AS based?

JL ANLEGG AS has its business address in Fyllingsdalen.

Property

Business address Vardesvingen 6B, 5141 Fyllingsdalen
Cadastral unit 4601-22/680/0/0
Building Rekkehus · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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