BIZTRAC BETA
Accounting and bookkeeping

BRENDEN & CO CONSULTING AS

Org. no. 913168240 Limited company (AS) Frogn Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 5,000
Equity NOK 213,000
Incorporated 2014
Share capital NOK 140,000

BRENDEN & CO CONSULTING AS is registered as a limited company in Frogn, Akershus with organisation number 913168240. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2014. Registered share capital is NOK 140,000, divided into 140 shares. The company's stated purpose is: “Å drive konsulentvirksomhet, regnskapstjenester, rådgivning og skattemessig bistand til sine kunder og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 5,000
Equity
NOK 213,000
Est. value
NOK 134,000

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.1%
Good
Equity as a share of total capital

Who owns BRENDEN & CO CONSULTING AS?

TBH AS
BRENDEN & CO CONSULTING AS
NOK 1.5m rev. · NOK 5,000 profit

BRENDEN & CO CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRENDEN & CO CONSULTING AS

Who owns BRENDEN & CO CONSULTING AS?

TBH AS is the largest registered owner, with 100.0%.

What is the revenue of BRENDEN & CO CONSULTING AS?

BRENDEN & CO CONSULTING AS had revenue of NOK 1.5m in 2025.

Who is the general manager of BRENDEN & CO CONSULTING AS?

Trude Folkøy Brenden is registered as general manager of BRENDEN & CO CONSULTING AS.

Where is BRENDEN & CO CONSULTING AS based?

BRENDEN & CO CONSULTING AS has its business address in Drøbak.

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.