BIZTRAC BETA
Construction of utility projects for electricity and telecommunications on land

BARSK ENTREPRENØR AS

Org. no. 812127012 Limited company (AS) Nordreisa Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 425,000
Operating profit NOK 172,000
Equity NOK 243,000
Incorporated 2013
Share capital NOK 100,000

BARSK ENTREPRENØR AS is registered as a limited company in Nordreisa, Troms with organisation number 812127012. The business is classified under construction of utility projects for electricity and telecommunications on land (NACE 42.222). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre tjenester innen høyspenningsanlegg og det som naturlig følger av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 425,000 in revenue and NOK 172,000 in operating profit.

Key figures · 2025

Revenue
NOK 425,000
Operating profit
NOK 172,000
Equity
NOK 243,000
Est. value
NOK 642,000

Financial health · 2025

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

Who owns BARSK ENTREPRENØR AS?

HARALD LYNGMO
BARSK ENTREPRENØR AS
NOK 425,000 rev. · NOK 172,000 profit

BARSK ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARSK ENTREPRENØR AS

Who owns BARSK ENTREPRENØR AS?

HARALD LYNGMO is the largest registered owner, with 100.0%.

What is the revenue of BARSK ENTREPRENØR AS?

BARSK ENTREPRENØR AS had revenue of NOK 425,000 in 2025.

Who is the general manager of BARSK ENTREPRENØR AS?

Harald Lyngmo is registered as general manager of BARSK ENTREPRENØR AS.

Where is BARSK ENTREPRENØR AS based?

BARSK ENTREPRENØR AS has its business address in Storslett.

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.