BIZTRAC BETA
Construction of residential and non-residential buildings

BERING BYGG AS

Org. no. 935726425 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 190,000
Equity NOK 164,000
Incorporated 2025
Employees 5
Share capital NOK 30,000

BERING BYGG AS is registered as a limited company in Tromsø, Troms with organisation number 935726425. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å drive med byggevirksomhet, herunder oppføring av bygninger, rehabilitering, vedlikehold, kjøp og salg av fast eiendom, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 190,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 190,000
Equity
NOK 164,000
Est. value
NOK 718,000

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.3%
Satisfactory
Equity as a share of total capital

Who owns BERING BYGG AS?

VIKTOR LAZAREV
BERING BYGG AS
NOK 3.5m rev. · NOK 190,000 profit

BERING BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERING BYGG AS

Who owns BERING BYGG AS?

VIKTOR LAZAREV is the largest registered owner, with 100.0%.

What is the revenue of BERING BYGG AS?

BERING BYGG AS had revenue of NOK 3.5m in 2025.

Who is the general manager of BERING BYGG AS?

Viktor Lazarev is registered as general manager of BERING BYGG AS.

Where is BERING BYGG AS based?

BERING BYGG AS has its business address in Kvaløysletta.

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.