biztrac. BETA
COMPANY REGISTER PROFILE
928995313 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other support activities to arts and performing arts

GUILDENSTERN AS

Org. no. 928995313 Limited company (AS) Oslo Incorporated 2022 Active
Revenue 2025 NOK 868,000
Operating profit NOK 132,000
Equity NOK 133,000
Incorporated 2022
Share capital NOK 30,000

GUILDENSTERN AS is registered as a limited company in Oslo, Oslo with organisation number 928995313. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kunstnerisk virksomhet. Salg av varer og tjenester innenfor kultur.”. The most recent filed accounts, for the 2025 financial year, show NOK 868,000 in revenue and NOK 132,000 in operating profit.

Key figures · 2025

Revenue
NOK 868,000
▲ +11 %
Operating profit
NOK 132,000
▲ +297 %
Equity
NOK 133,000
▲ +532 %
Est. value
NOK 573,000

Financial health · 2025

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

Who owns GUILDENSTERN AS?

GUILDENSTERN AS
NOK 868,000 rev. · NOK 132,000 profit

GUILDENSTERN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GUILDENSTERN AS er morselskap for 1 datterselskap:

Frequently asked questions about GUILDENSTERN AS

Who owns GUILDENSTERN AS?

GUILDENSTERN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GUILDENSTERN AS?

GUILDENSTERN AS had revenue of NOK 868,000 in 2025.

Who is the general manager of GUILDENSTERN AS?

Frode Gjerløw is registered as general manager of GUILDENSTERN AS.

Where is GUILDENSTERN AS based?

GUILDENSTERN AS has its business address in Oslo.

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.