BIZTRAC BETA
COMPANY REGISTER PROFILE
915898262 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

LTST AS

Org. no. 915898262 Limited company (AS) Hammerfest Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 121,000
Equity NOK 389,000
Incorporated 2015
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-24 Adresseendring registrert 2026-06-24.

LTST AS is registered as a limited company in Hammerfest, Finnmark with organisation number 915898262. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å føre regnskap for andre, sjåførtjenester og salg av egen produsert ved.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 121,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
▲ +23 %
Operating profit
NOK 121,000
▼ −24 %
Equity
NOK 389,000
▲ +18 %
Est. value
NOK 698,000

Financial health · 2025

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
9.7%
Satisfactory
Return on total assets
Solidity
27.3%
Good
Equity as a share of total capital

Who owns LTST AS?

LTST AS
NOK 5.6m rev. · NOK 121,000 profit

LTST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LTST AS

Who owns LTST AS?

LILLIAN THORESEN is the largest registered owner, with 100.0%.

What is the revenue of LTST AS?

LTST AS had revenue of NOK 5.6m in 2025.

Who is the general manager of LTST AS?

Lena Hansen Montalvao is registered as general manager of LTST AS.

Where is LTST AS based?

LTST AS has its business address in Hammerfest.

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.