BIZTRAC BETA
Uoppgitt

LANGLI-INVEST AS

Org. no. 926182773 Limited company (AS) Nærøysund Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 7.4m
Incorporated 2020
Share capital NOK 1.3m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

LANGLI-INVEST AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 926182773. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 1.3m, divided into 1288000 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, utlånsvirksomhet, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette. Selskapet kan også kan også ha konsulentvirksomhet, samt yte konserninterne tjenester.”.

Key figures · 2024

Operating profit
NOK −18,000
Equity
NOK 7.4m
Est. value
NOK 15.7m

Financial health · 2024

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

Who owns LANGLI-INVEST AS?

GISLE LANGLI
LANGLI-INVEST AS
· NOK −18,000 profit

LANGLI-INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LANGLI-INVEST AS own?

LANGLI-INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about LANGLI-INVEST AS

Who owns LANGLI-INVEST AS?

GISLE LANGLI is the largest registered owner, with 100.0%.

Who is the general manager of LANGLI-INVEST AS?

Gisle Langli is registered as general manager of LANGLI-INVEST AS.

Where is LANGLI-INVEST AS based?

LANGLI-INVEST AS has its business address in Rørvik.

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.