BIZTRAC BETA
Accounting and bookkeeping

EKSTERN REGNSKAP AS

Org. no. 966313404 Limited company (AS) Båtsfjord Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 69,000
Equity NOK 210,000
Incorporated 1993
Employees 9
Share capital NOK 100,000

EKSTERN REGNSKAP AS is registered as a limited company in Båtsfjord, Finnmark with organisation number 966313404. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1993 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tilby regnskapstjenester og annen beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 69,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 69,000
Equity
NOK 210,000
Est. value
NOK 321,000

Financial health · 2024

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

Who owns EKSTERN REGNSKAP AS?

ERLING NYSTAD
EKSTERN REGNSKAP AS
NOK 9.5m rev. · NOK 69,000 profit

EKSTERN REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EKSTERN REGNSKAP AS own?

EKSTERN REGNSKAP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EKSTERN REGNSKAP AS

Who owns EKSTERN REGNSKAP AS?

ERLING NYSTAD is the largest registered owner, with 100.0%.

What is the revenue of EKSTERN REGNSKAP AS?

EKSTERN REGNSKAP AS had revenue of NOK 9.5m in 2024.

Who is the general manager of EKSTERN REGNSKAP AS?

Erling Nystad is registered as general manager of EKSTERN REGNSKAP AS.

Where is EKSTERN REGNSKAP AS based?

EKSTERN REGNSKAP AS has its business address in Båtsfjord.

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.