BIZTRAC BETA
Retail sale of flowers, plants, seeds and fertilisers

BISLETT BLOMSTER SERVICE AS

Org. no. 925385298 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 648,000
Operating profit NOK 148,000
Equity NOK 470,000
Incorporated 2020
Share capital NOK 30,000

BISLETT BLOMSTER SERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 925385298. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selger og leverer blomsterdekorasjoner mm.”. The most recent filed accounts, for the 2024 financial year, show NOK 648,000 in revenue and NOK 148,000 in operating profit.

Key figures · 2024

Revenue
NOK 648,000
Operating profit
NOK 148,000
Equity
NOK 470,000
Est. value
NOK 778,000

Financial health · 2024

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

Who owns BISLETT BLOMSTER SERVICE AS?

KATHINKA HOLDING AS
BISLETT BLOMSTER SERVICE AS
NOK 648,000 rev. · NOK 148,000 profit

BISLETT BLOMSTER SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BISLETT BLOMSTER SERVICE AS

Who owns BISLETT BLOMSTER SERVICE AS?

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

What is the revenue of BISLETT BLOMSTER SERVICE AS?

BISLETT BLOMSTER SERVICE AS had revenue of NOK 648,000 in 2024.

Who is the general manager of BISLETT BLOMSTER SERVICE AS?

Linn Kathinka Hanevold is registered as general manager of BISLETT BLOMSTER SERVICE AS.

Where is BISLETT BLOMSTER SERVICE AS based?

BISLETT BLOMSTER SERVICE 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.