biztrac. BETA
COMPANY REGISTER PROFILE
936199666 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other performing arts activities

GAUSEMEL AS

Org. no. 936199666 Limited company (AS) Bodø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 19,000
Operating profit NOK 16,000
Equity NOK 26,000
Incorporated 2025
Share capital NOK 30,000

GAUSEMEL AS is registered as a limited company in Bodø, Nordland with organisation number 936199666. The business is classified under other performing arts activities (NACE 90.209). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen foredrag, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 19,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 19,000
Operating profit
NOK 16,000
Equity
NOK 26,000
Est. value
NOK 64,000

Financial health · 2025

Liquidity
2.94
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
66.0%
Weak
Equity as a share of total capital

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

Who owns GAUSEMEL AS?

GAUSEMEL AS
NOK 19,000 rev. · NOK 16,000 profit

GAUSEMEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAUSEMEL AS

Who owns GAUSEMEL AS?

Tor Gausemel Kristensen is the largest registered owner, with 100.0%.

What is the revenue of GAUSEMEL AS?

GAUSEMEL AS had revenue of NOK 19,000 in 2025.

Who is the general manager of GAUSEMEL AS?

Tor Gausemel Kristensen is registered as general manager of GAUSEMEL AS.

Where is GAUSEMEL AS based?

GAUSEMEL AS has its business address in Bodø.

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.