biztrac. BETA
COMPANY REGISTER PROFILE
927049473 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

BRGT CONSULTING AS

Org. no. 927049473 Limited company (AS) Stavanger Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 17,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

BRGT CONSULTING AS is registered as a limited company in Stavanger, Rogaland with organisation number 927049473. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bedriftsrådgivning og annen administrativ rådgivning, samt investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
▼ −6 %
Equity
NOK 17,000
▼ −25 %
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns BRGT CONSULTING AS?

BRGT CONSULTING AS
NOK 0 rev. · NOK −6,000 profit

BRGT CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRGT CONSULTING AS

Who owns BRGT CONSULTING AS?

Bjørn-Robin Garland-Thomas is the largest registered owner, with 100.0%.

What is the revenue of BRGT CONSULTING AS?

BRGT CONSULTING AS had revenue of NOK 0 in 2025.

Where is BRGT CONSULTING AS based?

BRGT CONSULTING AS has its business address in Stavanger.

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.