BIZTRAC BETA
Rental and operating of own or leased real estate

LASKEN TUNET AS

Org. no. 933672719 Limited company (AS) Larvik Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.6m
Equity NOK 7.5m
Incorporated 1983
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LASKEN TUNET AS is registered as a limited company in Larvik, Vestfold with organisation number 933672719. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1983. Registered share capital is NOK 100,000. The company's stated purpose is: “Utvikle, eie og drifte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.6m
Equity
NOK 7.5m
Est. value
NOK 8.6m

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.1%
Very good
Equity as a share of total capital

Who owns LASKEN TUNET AS?

NG EIENDOM VESTFOLD TELEMARK AS
LASKEN TUNET AS
NOK 2.2m rev. · NOK 1.6m profit

LASKEN TUNET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LASKEN TUNET AS er morselskap for 249 datterselskaper:

Frequently asked questions about LASKEN TUNET AS

Who owns LASKEN TUNET AS?

NG EIENDOM VESTFOLD TELEMARK AS is the largest registered owner, with 100.0%.

What is the revenue of LASKEN TUNET AS?

LASKEN TUNET AS had revenue of NOK 2.2m in 2024.

Who is the general manager of LASKEN TUNET AS?

Torgeir Herlofsen is registered as general manager of LASKEN TUNET AS.

Where is LASKEN TUNET AS based?

LASKEN TUNET AS has its business address in Larvik.

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.