BIZTRAC BETA
Construction of residential and non-residential buildings

LIERNE MESTERBYGG AS

Org. no. 989932519 Limited company (AS) Lierne Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 245,000
Operating profit NOK 12,000
Equity NOK 9.6m
Incorporated 2006
Share capital NOK 100,000

LIERNE MESTERBYGG AS is registered as a limited company in Lierne, Trøndelag with organisation number 989932519. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å foreta investeringer i aksjer og fast eiendom og utleie av fast eiendom, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 245,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 245,000
Operating profit
NOK 12,000
Equity
NOK 9.6m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns LIERNE MESTERBYGG AS?

TERJE HOMO
LIERNE MESTERBYGG AS
NOK 245,000 rev. · NOK 12,000 profit

LIERNE MESTERBYGG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LIERNE MESTERBYGG AS own?

LIERNE MESTERBYGG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LIERNE MESTERBYGG AS

Who owns LIERNE MESTERBYGG AS?

TERJE HOMO is the largest registered owner, with 33.3%.

What is the revenue of LIERNE MESTERBYGG AS?

LIERNE MESTERBYGG AS had revenue of NOK 245,000 in 2025.

Where is LIERNE MESTERBYGG AS based?

LIERNE MESTERBYGG AS has its business address in Nordli.

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.