BIZTRAC BETA
Development of building projects

TL SOLUTIONS AS

Org. no. 994449540 Limited company (AS) Asker Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 297,000
Operating profit NOK 178,000
Equity NOK −49,000
Incorporated 2009
Share capital NOK 120,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−49k kr).

TL SOLUTIONS AS is registered as a limited company in Asker, Akershus with organisation number 994449540. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2009. Registered share capital is NOK 120,000, divided into 10000 shares. The company's stated purpose is: “Entreprenørvirksomhet og utvikling og salg av eiendom. Trading av kjøretøy, båter og varepartier.”. The most recent filed accounts, for the 2025 financial year, show NOK 297,000 in revenue and NOK 178,000 in operating profit.

Key figures · 2025

Revenue
NOK 297,000
Operating profit
NOK 178,000
Equity
NOK −49,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-136.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TL SOLUTIONS AS?

BLESS HOLDING AS
TL SOLUTIONS AS
NOK 297,000 rev. · NOK 178,000 profit

TL SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TL SOLUTIONS AS

Who owns TL SOLUTIONS AS?

BLESS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TL SOLUTIONS AS?

TL SOLUTIONS AS had revenue of NOK 297,000 in 2025.

Who is the general manager of TL SOLUTIONS AS?

Lars-Petter Larsen is registered as general manager of TL SOLUTIONS AS.

Where is TL SOLUTIONS AS based?

TL SOLUTIONS AS has its business address in Spikkestad.

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.