BIZTRAC BETA
Construction of utility projects for fluids

BJELLAND BRØNN OG ANLEGG AS

Org. no. 928737977 Limited company (AS) Lindesnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 9.4m
Operating profit NOK 1.2m
Equity NOK 348,000
Incorporated 2022
Share capital NOK 150,000

BJELLAND BRØNN OG ANLEGG AS is registered as a limited company in Lindesnes, Agder with organisation number 928737977. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 2022. Registered share capital is NOK 150,000, divided into 1 shares. The company's stated purpose is: “Brønnboring, anleggsarbeid og salg av varer og tjenester som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.4m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 9.4m
Operating profit
NOK 1.2m
Equity
NOK 348,000
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

Who owns BJELLAND BRØNN OG ANLEGG AS?

THOMAS SKULAND
BJELLAND BRØNN OG ANLEGG AS
NOK 9.4m rev. · NOK 1.2m profit

BJELLAND BRØNN OG ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJELLAND BRØNN OG ANLEGG AS

Who owns BJELLAND BRØNN OG ANLEGG AS?

THOMAS SKULAND is the largest registered owner, with 100.0%.

What is the revenue of BJELLAND BRØNN OG ANLEGG AS?

BJELLAND BRØNN OG ANLEGG AS had revenue of NOK 9.4m in 2024.

Who is the general manager of BJELLAND BRØNN OG ANLEGG AS?

Thomas Skuland is registered as general manager of BJELLAND BRØNN OG ANLEGG AS.

Where is BJELLAND BRØNN OG ANLEGG AS based?

BJELLAND BRØNN OG ANLEGG AS has its business address in Bjelland.

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.