BIZTRAC BETA
COMPANY REGISTER PROFILE
976633253 ORG. NO. 2020 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

MAGS KONSULT SCHØYEN

Org. no. 976633253 Sole proprietorship (ENK) Bærum Active
Ownership graph ↗
Revenue 2020 NOK 917,000
Operating profit NOK 405,000
Equity NOK 456,000

MAGS KONSULT SCHØYEN is registered as a sole proprietorship in Bærum, Akershus with organisation number 976633253. The business is classified under business and other management consultancy activities (NACE 70.200). The most recent filed accounts, for the 2020 financial year, show NOK 917,000 in revenue and NOK 405,000 in operating profit.

Former names: MAGS REGNSKAP Morten Schøyen

Key figures · 2020

Revenue
NOK 917,000
Operating profit
NOK 405,000
Equity
NOK 456,000
Est. value
NOK 1.6m

Financial health · 2020

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

Who owns MAGS KONSULT SCHØYEN?

No shareholders are registered for MAGS KONSULT SCHØYEN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MAGS KONSULT SCHØYEN

What is the revenue of MAGS KONSULT SCHØYEN?

MAGS KONSULT SCHØYEN had revenue of NOK 917,000 in 2020.

Where is MAGS KONSULT SCHØYEN based?

MAGS KONSULT SCHØYEN has its business address in Eiksmarka.

Property

Business address Jøssingveien 90, 1359 Eiksmarka
Cadastral unit 3201-28/15/0/0
Building Enebolig · 1 unit

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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