BIZTRAC BETA
Accounting and bookkeeping

BRAATHEN & PARTNERS AS

Org. no. 879738342 Limited company (AS) Lørenskog Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 12.6m
Operating profit NOK 1.0m
Equity NOK 2.6m
Incorporated 1998
Employees 12
Share capital NOK 100,000

BRAATHEN & PARTNERS AS is registered as a limited company in Lørenskog, Akershus with organisation number 879738342. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1998 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Rådgivning og bistand innen IT, økonomi og regnskap. Regnskapstjenester. Administrative tjenester. Kjøp og salg av aksjer og fond.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.6m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 12.6m
Operating profit
NOK 1.0m
Equity
NOK 2.6m
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.4%
Very good
Equity as a share of total capital

Who owns BRAATHEN & PARTNERS AS?

LASSE BALCHEN BRAATHEN
BRAATHEN & PARTNERS AS
NOK 12.6m rev. · NOK 1.0m profit

BRAATHEN & PARTNERS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRAATHEN & PARTNERS AS

Who owns BRAATHEN & PARTNERS AS?

LASSE BALCHEN BRAATHEN is the largest registered owner, with 50.0%.

What is the revenue of BRAATHEN & PARTNERS AS?

BRAATHEN & PARTNERS AS had revenue of NOK 12.6m in 2025.

Who is the general manager of BRAATHEN & PARTNERS AS?

Lasse Balchen Braathen is registered as general manager of BRAATHEN & PARTNERS AS.

Where is BRAATHEN & PARTNERS AS based?

BRAATHEN & PARTNERS AS has its business address in Rasta.

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.