BIZTRAC BETA
COMPANY REGISTER PROFILE
915833780 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

TLANGHOLEN INVEST AS

Org. no. 915833780 Limited company (AS) Vestby Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 4.7m
Incorporated 2015
Share capital NOK 1.4m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

TLANGHOLEN INVEST AS is registered as a limited company in Vestby, Akershus with organisation number 915833780. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 1.4m, divided into 88 shares. The company's stated purpose is: “Investering og deltagelse i andre selskaper gjennom aksjebesittelse eller på annen måte.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −3 %
Equity
NOK 4.7m
▲ +11 %
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
197.48
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns TLANGHOLEN INVEST AS?

TLANGHOLEN INVEST AS
· NOK −8,000 profit

TLANGHOLEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TLANGHOLEN INVEST AS

Who owns TLANGHOLEN INVEST AS?

TORGEIR LANGHOLEN is the largest registered owner, with 100.0%.

Where is TLANGHOLEN INVEST AS based?

TLANGHOLEN INVEST AS has its business address in Vestby.

Property

Business address Balders vei 11, 1540 Vestby
Cadastral unit 3216-9/203/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.