BIZTRAC BETA
Other educational support services n.e.c.

RESSURSAKADEMIET AS

Org. no. 925665665 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 1,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

RESSURSAKADEMIET AS is registered as a limited company in Drammen, Buskerud with organisation number 925665665. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av kurs, opplæring, pedagogisk tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 1,000
Est. value
NOK 2,000

Financial health · 2025

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

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

Who owns RESSURSAKADEMIET AS?

JANNE TVEIT STENSRUD
RESSURSAKADEMIET AS
NOK 0 rev. · NOK −16,000 profit

RESSURSAKADEMIET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESSURSAKADEMIET AS

Who owns RESSURSAKADEMIET AS?

JANNE TVEIT STENSRUD is the largest registered owner, with 100.0%.

What is the revenue of RESSURSAKADEMIET AS?

RESSURSAKADEMIET AS had revenue of NOK 0 in 2025.

Who is the general manager of RESSURSAKADEMIET AS?

Janne Tveit Stensrud is registered as general manager of RESSURSAKADEMIET AS.

Where is RESSURSAKADEMIET AS based?

RESSURSAKADEMIET AS has its business address in Drammen.

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.