BIZTRAC BETA
Manufacture of furniture

TREKLANG AS

Org. no. 997163664 Limited company (AS) Eidskog Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 21,000
Operating profit NOK −39,000
Equity NOK −16,000
Incorporated 2011
Share capital NOK 150,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−16k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39k kr).

TREKLANG AS is registered as a limited company in Eidskog, Innlandet with organisation number 997163664. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 2011. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Utvikle, produsere og selge møbler og andre treprodukter, samt annen næringsvirksomhet herunder musikk og underholdning.”. The most recent filed accounts, for the 2024 financial year, show NOK 21,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 21,000
Operating profit
NOK −39,000
Equity
NOK −16,000

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.7%
Weak
Equity as a share of total capital

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

Who owns TREKLANG AS?

Espen Thorstensen
TREKLANG AS
NOK 21,000 rev. · NOK −39,000 profit

TREKLANG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TREKLANG AS

Who owns TREKLANG AS?

Espen Thorstensen is the largest registered owner, with 100.0%.

What is the revenue of TREKLANG AS?

TREKLANG AS had revenue of NOK 21,000 in 2024.

Who is the general manager of TREKLANG AS?

Espen Thorstensen is registered as general manager of TREKLANG AS.

Where is TREKLANG AS based?

TREKLANG AS has its business address in Skotterud.

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.