biztrac. BETA
COMPANY REGISTER PROFILE
936200338 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

EFFEKTIV REGNSKAPSSERVICE AS

Org. no. 936200338 Limited company (AS) Tromsø Incorporated 1985 Active
Revenue 2025 NOK 7.3m
Operating profit NOK 2.5m
Equity NOK 2.9m
Incorporated 1985
Share capital NOK 100,000

EFFEKTIV REGNSKAPSSERVICE AS is registered as a limited company in Tromsø, Troms with organisation number 936200338. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1985. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Regnskap og konsulenttjenester for nærings- livet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.3m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 7.3m
▼ −1 %
Operating profit
NOK 2.5m
▼ −11 %
Equity
NOK 2.9m
▲ +3 %
Est. value
NOK 9.8m

Financial health · 2025

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

Who owns EFFEKTIV REGNSKAPSSERVICE AS?

EFFEKTIV REGNSKAPSSERVICE AS
NOK 7.3m rev. · NOK 2.5m profit

EFFEKTIV REGNSKAPSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EFFEKTIV REGNSKAPSSERVICE AS

Who owns EFFEKTIV REGNSKAPSSERVICE AS?

Jan Blomseth is the largest registered owner, with 100.0%.

What is the revenue of EFFEKTIV REGNSKAPSSERVICE AS?

EFFEKTIV REGNSKAPSSERVICE AS had revenue of NOK 7.3m in 2025.

Who is the general manager of EFFEKTIV REGNSKAPSSERVICE AS?

Jeanette-Iren Aandal is registered as general manager of EFFEKTIV REGNSKAPSSERVICE AS.

Where is EFFEKTIV REGNSKAPSSERVICE AS based?

EFFEKTIV REGNSKAPSSERVICE AS has its business address in Tromsø.

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.