BIZTRAC BETA
Rental and operating of own or leased real estate

SKARPSNO AS

Org. no. 979714033 Limited company (AS) Lillehammer Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 2.3m
Equity NOK 75.9m
Incorporated 1998
Share capital NOK 1.6m

SKARPSNO AS is registered as a limited company in Lillehammer, Innlandet with organisation number 979714033. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 1.6m, divided into 18000 shares. The company's stated purpose is: “Eiendomsutvikling, herunder drift av fast eiendom samt investering i verdipapirer og alt som står i naturlig forbindelse med dette, samt å gi støtte til veldedige og allmennyttige formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 2.3m
Equity
NOK 75.9m
Est. value
NOK 58.4m

Financial health · 2025

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

Who owns SKARPSNO AS?

PER TORE TEKSUM
SKARPSNO AS
NOK 6.1m rev. · NOK 2.3m profit

SKARPSNO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKARPSNO AS own?

SKARPSNO AS holds stakes in 27 companies:

See the full ownership structure →

Frequently asked questions about SKARPSNO AS

Who owns SKARPSNO AS?

PER TORE TEKSUM is the largest registered owner, with 100.0%.

What is the revenue of SKARPSNO AS?

SKARPSNO AS had revenue of NOK 6.1m in 2025.

Who is the general manager of SKARPSNO AS?

Stian Ryen is registered as general manager of SKARPSNO AS.

Where is SKARPSNO AS based?

SKARPSNO AS has its business address in Lillehammer.

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.