biztrac. BETA
COMPANY REGISTER PROFILE
835050092 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of veneer sheets and wood-based panels

LANGLO INTERIØR AS

Org. no. 835050092 Limited company (AS) Stranda Incorporated 2025 Active
Operating profit NOK −5,000
Equity NOK 20,000
Incorporated 2025
Employees 15
Share capital NOK 30,000

Signals

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

LANGLO INTERIØR AS is registered as a limited company in Stranda, Møre og Romsdal with organisation number 835050092. The business is classified under manufacture of veneer sheets and wood-based panels (NACE 16.210). The company was incorporated in 2025 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon og handelsvirksomhet og det som står i naturlig forbindelse med dette, samt annen økonomisk virksomhet, inkludert deltakelse i andre selskaper.”.

Former names: AXXELERATOR 11 AS

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 20,000
Est. value
NOK 23,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LANGLO INTERIØR AS?

LANGLO INTERIØR AS
· NOK −5,000 profit

LANGLO INTERIØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGLO INTERIØR AS

Who owns LANGLO INTERIØR AS?

TIME INTERIØR HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of LANGLO INTERIØR AS?

Jan Rune Svihus is registered as general manager of LANGLO INTERIØR AS.

Where is LANGLO INTERIØR AS based?

LANGLO INTERIØR AS has its business address in Stranda.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.