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

NIVÅMETODEN AS

Org. no. 932516365 Limited company (AS) Nesodden Incorporated 1976 Active
Ownership graph ↗
Revenue 2024 NOK 32,000
Operating profit NOK 21,000
Equity NOK −178,000
Incorporated 1976
Share capital NOK 690,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−178k kr).

NIVÅMETODEN AS is registered as a limited company in Nesodden, Akershus with organisation number 932516365. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 1976. Registered share capital is NOK 690,000, divided into 92 shares. The company's stated purpose is: “Å drive utvikling, informasjon og opplæring i kommunikasjon og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 32,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2024

Revenue
NOK 32,000
Operating profit
NOK 21,000
Equity
NOK −178,000
Est. value
NOK 110,000

Financial health · 2024

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

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

Who owns NIVÅMETODEN AS?

TORMOD BJØRNSTAD
NIVÅMETODEN AS
NOK 32,000 rev. · NOK 21,000 profit

NIVÅMETODEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIVÅMETODEN AS

Who owns NIVÅMETODEN AS?

TORMOD BJØRNSTAD is the largest registered owner, with 100.0%.

What is the revenue of NIVÅMETODEN AS?

NIVÅMETODEN AS had revenue of NOK 32,000 in 2024.

Who is the general manager of NIVÅMETODEN AS?

Tormod Bjørnstad is registered as general manager of NIVÅMETODEN AS.

Where is NIVÅMETODEN AS based?

NIVÅMETODEN AS has its business address in Nesodden.

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.