BIZTRAC BETA
Accounting and bookkeeping

BRUNLANES REGNSKAP AS

Org. no. 925178276 Limited company (AS) Larvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 24,000
Equity NOK 37,000
Incorporated 2020
Employees 6
Share capital NOK 100,000

BRUNLANES REGNSKAP AS is registered as a limited company in Larvik, Vestfold with organisation number 925178276. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2020 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Regnskapsførsel og økonomisk rådgivning og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 24,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 24,000
Equity
NOK 37,000
Est. value
NOK 96,000

Financial health · 2024

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

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

Who owns BRUNLANES REGNSKAP AS?

AKSEL KNUTSEN
BRUNLANES REGNSKAP AS
NOK 4.7m rev. · NOK 24,000 profit

BRUNLANES REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRUNLANES REGNSKAP AS

Who owns BRUNLANES REGNSKAP AS?

AKSEL KNUTSEN is the largest registered owner, with 100.0%.

What is the revenue of BRUNLANES REGNSKAP AS?

BRUNLANES REGNSKAP AS had revenue of NOK 4.7m in 2024.

Who is the general manager of BRUNLANES REGNSKAP AS?

Aksel Knutsen is registered as general manager of BRUNLANES REGNSKAP AS.

Where is BRUNLANES REGNSKAP AS based?

BRUNLANES REGNSKAP AS has its business address in Larvik.

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.