BIZTRAC BETA
Construction of residential and non-residential buildings

ERIKSSON BYGGTJENESTER AS

Org. no. 913624793 Limited company (AS) Lierne Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 98,000
Equity NOK 161,000
Incorporated 2014
Share capital NOK 30,000

ERIKSSON BYGGTJENESTER AS is registered as a limited company in Lierne, Trøndelag with organisation number 913624793. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet, samt ved aksjer og parter delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 98,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 98,000
Equity
NOK 161,000
Est. value
NOK 322,000

Financial health · 2025

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

Who owns ERIKSSON BYGGTJENESTER AS?

LINDA CICILIE ERIKSSON
ERIKSSON BYGGTJENESTER AS
NOK 2.0m rev. · NOK 98,000 profit

ERIKSSON BYGGTJENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ERIKSSON BYGGTJENESTER AS

Who owns ERIKSSON BYGGTJENESTER AS?

LINDA CICILIE ERIKSSON is the largest registered owner, with 50.0%.

What is the revenue of ERIKSSON BYGGTJENESTER AS?

ERIKSSON BYGGTJENESTER AS had revenue of NOK 2.0m in 2025.

Who is the general manager of ERIKSSON BYGGTJENESTER AS?

Tor-Erik Eriksson is registered as general manager of ERIKSSON BYGGTJENESTER AS.

Where is ERIKSSON BYGGTJENESTER AS based?

ERIKSSON BYGGTJENESTER 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.