BIZTRAC BETA
Uoppgitt

TRINITY AS

Org. no. 930939587 Limited company (AS) Fauske Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 234,000
Operating profit NOK −39,000
Equity NOK 3.6m
Incorporated 2023
Share capital NOK 30,000

Signals

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

TRINITY AS is registered as a limited company in Fauske, Nordland with organisation number 930939587. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, rådgivning og personelltjenester eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 234,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 234,000
Operating profit
NOK −39,000
Equity
NOK 3.6m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns TRINITY AS?

EIVIND FRIDAHL
TRINITY AS
NOK 234,000 rev. · NOK −39,000 profit

TRINITY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRINITY AS own?

TRINITY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRINITY AS

Who owns TRINITY AS?

EIVIND FRIDAHL is the largest registered owner, with 100.0%.

What is the revenue of TRINITY AS?

TRINITY AS had revenue of NOK 234,000 in 2025.

Where is TRINITY AS based?

TRINITY AS has its business address in Fauske.

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.