biztrac. BETA
COMPANY REGISTER PROFILE
929882717 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Arts creation activities in literature

STARSEEDS AS

Org. no. 929882717 Limited company (AS) Nesodden Incorporated 2022 Active
Revenue 2025 NOK 848,000
Operating profit NOK 103,000
Equity NOK 62,000
Incorporated 2022
Share capital NOK 30,000

STARSEEDS AS is registered as a limited company in Nesodden, Akershus with organisation number 929882717. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Underholdning, media og utdanning, og det som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 848,000 in revenue and NOK 103,000 in operating profit.

Former names: THE JOLLY COMPANY AS

Key figures · 2025

Revenue
NOK 848,000
▼ −11 %
Operating profit
NOK 103,000
▲ +847 %
Equity
NOK 62,000
▲ +405 %
Est. value
NOK 411,000

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
63.7%
Very good
Return on total assets
Solidity
24.1%
Weak
Equity as a share of total capital

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

Who owns STARSEEDS AS?

STARSEEDS AS
NOK 848,000 rev. · NOK 103,000 profit

STARSEEDS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STARSEEDS AS

Who owns STARSEEDS AS?

Lisa Stokke Jolly is the largest registered owner, with 100.0%.

What is the revenue of STARSEEDS AS?

STARSEEDS AS had revenue of NOK 848,000 in 2025.

Who is the general manager of STARSEEDS AS?

Lisa Stokke Jolly is registered as general manager of STARSEEDS AS.

Where is STARSEEDS AS based?

STARSEEDS AS has its business address in Fjellstrand.

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.