BIZTRAC BETA
Computer consultancy and computer facilities management activities

TOPPIN AS

Org. no. 814012662 Limited company (AS) Ullensaker Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 7,000
Equity NOK 87,000
Incorporated 2014
Share capital NOK 30,000

TOPPIN AS is registered as a limited company in Ullensaker, Akershus with organisation number 814012662. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Skal arbeide for å fremme kjærlighet til naturen og hvordan tid i naturen kan bedre vår mentale helse. Vi jobber spesielt mot barn, unge, barnefamilier og personer med redusert funksjonsevne.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 7,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 7,000
Equity
NOK 87,000
Est. value
NOK 59,000

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.0%
Weak
Equity as a share of total capital

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

Who owns TOPPIN AS?

JAN-KRISTIAN REIERSTAD
TOPPIN AS
NOK 1.5m rev. · NOK 7,000 profit

TOPPIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPPIN AS

Who owns TOPPIN AS?

JAN-KRISTIAN REIERSTAD is the largest registered owner, with 50.0%.

What is the revenue of TOPPIN AS?

TOPPIN AS had revenue of NOK 1.5m in 2024.

Who is the general manager of TOPPIN AS?

Jan-Kristian Reierstad is registered as general manager of TOPPIN AS.

Where is TOPPIN AS based?

TOPPIN AS has its business address in Kløfta.

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.