BIZTRAC BETA
Accounting and bookkeeping

ELSO REGNSKAP AS

Org. no. 931475924 Limited company (AS) Nord-Fron Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 917,000
Operating profit NOK 41,000
Equity NOK 46,000
Incorporated 2023
Share capital NOK 30,000

ELSO REGNSKAP AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 931475924. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Regnskapsføring og konsulentvirksomhet, samt andre produkter/tjenester som naturlig hører sammen med dette. Selskapet kan også investere og delta i andre tilsvarende selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 917,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 917,000
Operating profit
NOK 41,000
Equity
NOK 46,000
Est. value
NOK 227,000

Financial health · 2025

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

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

Who owns ELSO REGNSKAP AS?

ESØ INVEST AS
ELSO REGNSKAP AS
NOK 917,000 rev. · NOK 41,000 profit

ELSO REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELSO REGNSKAP AS

Who owns ELSO REGNSKAP AS?

ESØ INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of ELSO REGNSKAP AS?

ELSO REGNSKAP AS had revenue of NOK 917,000 in 2025.

Who is the general manager of ELSO REGNSKAP AS?

Ellen Sofie Ødegården is registered as general manager of ELSO REGNSKAP AS.

Where is ELSO REGNSKAP AS based?

ELSO REGNSKAP AS has its business address in Vinstra.

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.