biztrac. BETA
COMPANY REGISTER PROFILE
986618678 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other education activities

OVERSKUDD OPPLÆRING AS

Org. no. 986618678 Limited company (AS) Bærum Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 291,000
Operating profit NOK 255,000
Equity NOK 118,000
Incorporated 2004
Share capital NOK 118,000

OVERSKUDD OPPLÆRING AS is registered as a limited company in Bærum, Akershus with organisation number 986618678. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2004. Registered share capital is NOK 118,000, divided into 117647 shares. The company's stated purpose is: “Tilby, administrere og/eller organisere undervisning/opplæring. Selskapet kan også engasjere seg i investeringsvirksomhet og annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 291,000 in revenue and NOK 255,000 in operating profit.

Former names: WASTE AND CO2 AS, OVERSIKT AS

Key figures · 2025

Revenue
NOK 291,000
▼ −29 %
Operating profit
NOK 255,000
▼ −34 %
Equity
NOK 118,000
▲ +0 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
26.5%
Very good
Return on total assets
Solidity
10.8%
Satisfactory
Equity as a share of total capital

Who owns OVERSKUDD OPPLÆRING AS?

OVERSKUDD OPPLÆRING AS
NOK 291,000 rev. · NOK 255,000 profit

OVERSKUDD OPPLÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OVERSKUDD OPPLÆRING AS

Who owns OVERSKUDD OPPLÆRING AS?

OVERSKUDD AS is the largest registered owner, with 100.0%.

What is the revenue of OVERSKUDD OPPLÆRING AS?

OVERSKUDD OPPLÆRING AS had revenue of NOK 291,000 in 2025.

Where is OVERSKUDD OPPLÆRING AS based?

OVERSKUDD OPPLÆRING AS has its business address in Hosle.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.