BIZTRAC BETA
COMPANY REGISTER PROFILE
924509716 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

SKARPSNO INVEST AS

Org. no. 924509716 Limited company (AS) Aurskog-Høland Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 82,000
Operating profit NOK 8,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 30,000

SKARPSNO INVEST AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 924509716. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap. Investering i aksjer og øvrige verdipapirer samt kjøp, salg og utleie av eiendom. I tillegg skal selskapet kunne drive med salg og produksjon av ved.”. The most recent filed accounts, for the 2025 financial year, show NOK 82,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 82,000
Operating profit
NOK 8,000
Equity
NOK 1.2m
Est. value
NOK 655,000

Financial health · 2025

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

Who owns SKARPSNO INVEST AS?

SAMUEL SKARPSNO
SKARPSNO INVEST AS
NOK 82,000 rev. · NOK 8,000 profit

SKARPSNO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKARPSNO INVEST AS

Who owns SKARPSNO INVEST AS?

SAMUEL SKARPSNO is the largest registered owner, with 100.0%.

What is the revenue of SKARPSNO INVEST AS?

SKARPSNO INVEST AS had revenue of NOK 82,000 in 2025.

Who is the general manager of SKARPSNO INVEST AS?

Samuel Skarpsno is registered as general manager of SKARPSNO INVEST AS.

Where is SKARPSNO INVEST AS based?

SKARPSNO INVEST AS has its business address in Aurskog.

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.