BIZTRAC BETA
Other specialised construction activities n.e.c.

LTS BETONGGULV AS

Org. no. 935226260 Limited company (AS) Froland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 11.3m
Operating profit NOK 29,000
Equity NOK 101,000
Incorporated 2025
Employees 11
Share capital NOK 80,000

LTS BETONGGULV AS is registered as a limited company in Froland, Agder with organisation number 935226260. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2025 and has 11 registered employees. Registered share capital is NOK 80,000, divided into 100 shares. The company's stated purpose is: “Betong- og tømrerarbeid og annet spesialisert bygge- og anleggsarbeid, ingeniørtjenester og hva som naturlig hører sammen med dette. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.3m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.3m
Operating profit
NOK 29,000
Equity
NOK 101,000
Est. value
NOK 156,000

Financial health · 2025

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.0%
Weak
Equity as a share of total capital

Who owns LTS BETONGGULV AS?

TN GROUP AS
LTS BETONGGULV AS
NOK 11.3m rev. · NOK 29,000 profit

LTS BETONGGULV AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LTS BETONGGULV AS

Who owns LTS BETONGGULV AS?

TN GROUP AS is the largest registered owner, with 25.0%.

What is the revenue of LTS BETONGGULV AS?

LTS BETONGGULV AS had revenue of NOK 11.3m in 2025.

Who is the general manager of LTS BETONGGULV AS?

Tomas Navardauskas is registered as general manager of LTS BETONGGULV AS.

Where is LTS BETONGGULV AS based?

LTS BETONGGULV AS has its business address in Froland.

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.