BIZTRAC BETA
Construction of residential and non-residential buildings

NORBYGG TRONDHEIM AS

Org. no. 920335772 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK 12,000
Equity NOK 823,000
Incorporated 2018
Employees 6
Share capital NOK 30,000

NORBYGG TRONDHEIM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920335772. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive med tømrervirksomhet samt annen nærliggende virksomhet. Selskapet kan også erverve aksjer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK 12,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK 12,000
Equity
NOK 823,000
Est. value
NOK 386,000

Financial health · 2024

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

Who owns NORBYGG TRONDHEIM AS?

OVE MEEK
NORBYGG TRONDHEIM AS
NOK 10.7m rev. · NOK 12,000 profit

NORBYGG TRONDHEIM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORBYGG TRONDHEIM AS

Who owns NORBYGG TRONDHEIM AS?

OVE MEEK is the largest registered owner, with 50.0%.

What is the revenue of NORBYGG TRONDHEIM AS?

NORBYGG TRONDHEIM AS had revenue of NOK 10.7m in 2024.

Who is the general manager of NORBYGG TRONDHEIM AS?

Ove Meek is registered as general manager of NORBYGG TRONDHEIM AS.

Where is NORBYGG TRONDHEIM AS based?

NORBYGG TRONDHEIM AS has its business address in Bosberg.

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.