BIZTRAC BETA
COMPANY REGISTER PROFILE
971048778 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Manufacture of ready-mixed concrete

TINGVOLL EIENDOM AS

Org. no. 971048778 Limited company (AS) Sortland Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 2.1m
Equity NOK 27.6m
Incorporated 1994
Share capital NOK 220,000

TINGVOLL EIENDOM AS is registered as a limited company in Sortland, Nordland with organisation number 971048778. The business is classified under manufacture of ready-mixed concrete (NACE 23.630). The company was incorporated in 1994. Registered share capital is NOK 220,000, divided into 220 shares. The company's stated purpose is: “Utleie av forretningseiendom samt annen virksomhet samt annen virksomhet som naturlig faller inn under dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
▲ +2 %
Operating profit
NOK 2.1m
▲ +115 %
Equity
NOK 27.6m
▲ +9 %
Est. value
NOK 21.9m

Financial health · 2025

Liquidity
3.60
Very good
Current assets ÷ current liabilities
Profitability
18.6%
Very good
Return on total assets
Solidity
80.0%
Very good
Equity as a share of total capital

Who owns TINGVOLL EIENDOM AS?

TINGVOLL EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TINGVOLL EIENDOM AS own?

TINGVOLL EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TINGVOLL EIENDOM AS

Who owns TINGVOLL EIENDOM AS?

ASBJØRN TORMOD EVEN TINGVOLL is the largest registered owner, with 59.5%.

What is the revenue of TINGVOLL EIENDOM AS?

TINGVOLL EIENDOM AS had revenue of NOK 2.9m in 2025.

Where is TINGVOLL EIENDOM AS based?

TINGVOLL EIENDOM AS has its business address in Sortland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.