BIZTRAC BETA
Other education activities

GOSSÉ CONSULTING AS

Org. no. 924971088 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 542,000
Operating profit NOK 522,000
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 30,000

GOSSÉ CONSULTING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 924971088. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Undervisning, rådgiving og annet som naturlig faller inn under dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagener.”. The most recent filed accounts, for the 2024 financial year, show NOK 542,000 in revenue and NOK 522,000 in operating profit.

Key figures · 2024

Revenue
NOK 542,000
Operating profit
NOK 522,000
Equity
NOK 1.6m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns GOSSÉ CONSULTING AS?

SIGURD GOSSE
GOSSÉ CONSULTING AS
NOK 542,000 rev. · NOK 522,000 profit

GOSSÉ CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GOSSÉ CONSULTING AS

Who owns GOSSÉ CONSULTING AS?

SIGURD GOSSE is the largest registered owner, with 100.0%.

What is the revenue of GOSSÉ CONSULTING AS?

GOSSÉ CONSULTING AS had revenue of NOK 542,000 in 2024.

Who is the general manager of GOSSÉ CONSULTING AS?

Sigurd Gosse is registered as general manager of GOSSÉ CONSULTING AS.

Where is GOSSÉ CONSULTING AS based?

GOSSÉ CONSULTING AS has its business address in Trondheim.

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.