biztrac. BETA
COMPANY REGISTER PROFILE
926516612 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in music

GULBRYNSANGER AS

Org. no. 926516612 Limited company (AS) Kvinesdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 345,000
Equity NOK 438,000
Incorporated 2021
Share capital NOK 30,000

GULBRYNSANGER AS is registered as a limited company in Kvinesdal, Agder with organisation number 926516612. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Innspilling og fremføring av musikk samt utvikling av artistkarriere og alt som naturlig hører inn under dette. Samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 345,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +122 %
Operating profit
NOK 345,000
▲ +434 %
Equity
NOK 438,000
▲ +198 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.98
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
49.8%
Very good
Equity as a share of total capital

Who owns GULBRYNSANGER AS?

GULBRYNSANGER AS
NOK 2.7m rev. · NOK 345,000 profit

GULBRYNSANGER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GULBRYNSANGER AS

Who owns GULBRYNSANGER AS?

Eirik Stakkeland is the largest registered owner, with 50.0%.

What is the revenue of GULBRYNSANGER AS?

GULBRYNSANGER AS had revenue of NOK 2.7m in 2025.

Who is the general manager of GULBRYNSANGER AS?

Eirik Stakkeland is registered as general manager of GULBRYNSANGER AS.

Where is GULBRYNSANGER AS based?

GULBRYNSANGER AS has its business address in Kvinlog.

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.