BIZTRAC BETA
Business and other management consultancy activities

TRINN 2 AS

Org. no. 984374720 Limited company (AS) Vestby Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −39,000
Equity NOK 2.8m
Incorporated 2002
Share capital NOK 100,000

Signals

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

TRINN 2 AS is registered as a limited company in Vestby, Akershus with organisation number 984374720. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Yte rådgivning til etablerere og små og mellomstore bedrifter, salg av tjenester til næringslivet og investere i eiendom og verdipapirer, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −39,000
Equity
NOK 2.8m
Est. value
NOK 15.0m

Financial health · 2024

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

Who owns TRINN 2 AS?

TROND KJETIL FREDSTAD
TRINN 2 AS
NOK 0 rev. · NOK −39,000 profit

TRINN 2 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRINN 2 AS own?

TRINN 2 AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TRINN 2 AS

Who owns TRINN 2 AS?

TROND KJETIL FREDSTAD is the largest registered owner, with 100.0%.

What is the revenue of TRINN 2 AS?

TRINN 2 AS had revenue of NOK 0 in 2024.

Where is TRINN 2 AS based?

TRINN 2 AS has its business address in Son.

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.