BIZTRAC BETA
Joinery installation

BERG BYGGTJENESTER AS

Org. no. 992887052 Limited company (AS) Levanger Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 11.2m
Operating profit NOK 886,000
Equity NOK 2.5m
Incorporated 2008
Employees 8
Share capital NOK 100,000

BERG BYGGTJENESTER AS is registered as a limited company in Levanger, Trøndelag with organisation number 992887052. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2008 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av snekkervirksomhet og investering i aksjer og lignende, samt hva hermed står i forbindelse herunder delta i andre virksomheter med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.2m in revenue and NOK 886,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.2m
Operating profit
NOK 886,000
Equity
NOK 2.5m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns BERG BYGGTJENESTER AS?

TYTTEBÆRVEIEN HOLDING AS
BERG BYGGTJENESTER AS
NOK 11.2m rev. · NOK 886,000 profit

BERG BYGGTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERG BYGGTJENESTER AS

Who owns BERG BYGGTJENESTER AS?

TYTTEBÆRVEIEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BERG BYGGTJENESTER AS?

BERG BYGGTJENESTER AS had revenue of NOK 11.2m in 2024.

Who is the general manager of BERG BYGGTJENESTER AS?

Per Åge Berg is registered as general manager of BERG BYGGTJENESTER AS.

Where is BERG BYGGTJENESTER AS based?

BERG BYGGTJENESTER AS has its business address in Levanger.

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.