BIZTRAC BETA
Other printing

KORTSHOP AS

Org. no. 991225951 Limited company (AS) Ålesund Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 10.8m
Operating profit NOK 421,000
Equity NOK 2.3m
Incorporated 2007
Employees 9
Share capital NOK 100,000

KORTSHOP AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 991225951. The business is classified under other printing (NACE 18.120). The company was incorporated in 2007 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg og trykking av trykksaker i forbindelse med bryllup, partnerskap, fødsel, dåp, navnedager, bursdager, konfirmasjoner og jul. Salg og utarbeiding av trykksaker til bedriftsmarkedet som visittkort, timekort, gavekort, invitasjoner, plakater, brosjyrer, internavis, kalendere og julekort.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.8m in revenue and NOK 421,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.8m
Operating profit
NOK 421,000
Equity
NOK 2.3m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns KORTSHOP AS?

KORTSHOP EIENDOM AS
KORTSHOP AS
NOK 10.8m rev. · NOK 421,000 profit

KORTSHOP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KORTSHOP AS

Who owns KORTSHOP AS?

KORTSHOP EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KORTSHOP AS?

KORTSHOP AS had revenue of NOK 10.8m in 2024.

Who is the general manager of KORTSHOP AS?

Vidar Strand is registered as general manager of KORTSHOP AS.

Where is KORTSHOP AS based?

KORTSHOP AS has its business address in Ålesund.

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.