BIZTRAC BETA
Accounting and bookkeeping

LØRENSKOG REGNSKAP AS

Org. no. 913191560 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 8.0m
Operating profit NOK 1.5m
Equity NOK 332,000
Incorporated 2014
Share capital NOK 30,000

LØRENSKOG REGNSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 913191560. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby regnskapstjenester, konsulenttjenester innen økonomi og administrasjon og kursvirksomhet. Selskapet skal også kunne delta i andre virksomheter med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.0m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 8.0m
Operating profit
NOK 1.5m
Equity
NOK 332,000
Est. value
NOK 6.8m

Financial health · 2025

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

Who owns LØRENSKOG REGNSKAP AS?

KRISTIN JOHANNE HØGLI
LØRENSKOG REGNSKAP AS
NOK 8.0m rev. · NOK 1.5m profit

LØRENSKOG REGNSKAP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØRENSKOG REGNSKAP AS

Who owns LØRENSKOG REGNSKAP AS?

KRISTIN JOHANNE HØGLI is the largest registered owner, with 45.0%.

What is the revenue of LØRENSKOG REGNSKAP AS?

LØRENSKOG REGNSKAP AS had revenue of NOK 8.0m in 2025.

Who is the general manager of LØRENSKOG REGNSKAP AS?

Thore Morten Eriksen is registered as general manager of LØRENSKOG REGNSKAP AS.

Where is LØRENSKOG REGNSKAP AS based?

LØRENSKOG REGNSKAP AS has its business address in Oslo.

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.