BIZTRAC BETA
Other captive investment companies

TRELAR AS

Org. no. 996889629 Limited company (AS) Moss Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 22,000
Operating profit NOK −67,000
Equity NOK 13.4m
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−67k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRELAR AS is registered as a limited company in Moss, Østfold with organisation number 996889629. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Foreta investeringer i andre selskaper, verdipapirer, eiendom og finansielle instrumenter og det som derved hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 22,000 in revenue and NOK −67,000 in operating profit.

Key figures · 2024

Revenue
NOK 22,000
Operating profit
NOK −67,000
Equity
NOK 13.4m
Est. value
NOK 9.4m

Financial health · 2024

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

Who owns TRELAR AS?

LARS IVAR TRETTETEIG
TRELAR AS
NOK 22,000 rev. · NOK −67,000 profit

TRELAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRELAR AS own?

TRELAR AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about TRELAR AS

Who owns TRELAR AS?

LARS IVAR TRETTETEIG is the largest registered owner, with 100.0%.

What is the revenue of TRELAR AS?

TRELAR AS had revenue of NOK 22,000 in 2024.

Where is TRELAR AS based?

TRELAR AS has its business address in Moss.

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.