BIZTRAC BETA
Rental and operating of own or leased real estate

LANGÅS HOLDING AS

Org. no. 920409806 Limited company (AS) Froland Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 190,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

LANGÅS HOLDING AS is registered as a limited company in Froland, Agder with organisation number 920409806. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringer i annen forretningsvirksomhet, herunder å delta i andre selskaper som aksjeeier eller ansvarlig deltaker, samt kjøp og salg av verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 190,000
Est. value
NOK 173,000

Financial health · 2024

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.2%
Weak
Equity as a share of total capital

Who owns LANGÅS HOLDING AS?

ANDERS LANGÅS
LANGÅS HOLDING AS
NOK 0 rev. · NOK −7,000 profit

LANGÅS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LANGÅS HOLDING AS own?

LANGÅS HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LANGÅS HOLDING AS

Who owns LANGÅS HOLDING AS?

ANDERS LANGÅS is the largest registered owner, with 100.0%.

What is the revenue of LANGÅS HOLDING AS?

LANGÅS HOLDING AS had revenue of NOK 0 in 2024.

Where is LANGÅS HOLDING AS based?

LANGÅS HOLDING AS has its business address in Arendal.

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.