BIZTRAC BETA
Other captive investment companies

NORWEGIAN BRIQUETTING AS

Org. no. 989240641 Limited company (AS) Porsgrunn Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 4.0m
Incorporated 2005
Share capital NOK 100,000

NORWEGIAN BRIQUETTING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 989240641. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og bestyre aksjer og eierparter i andre selskaper og alt som knytter seg til dette samt ved aksjetegning eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 4.0m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns NORWEGIAN BRIQUETTING AS?

FRODE AALTVEDT
NORWEGIAN BRIQUETTING AS
NOK 0 rev. · NOK 0 profit

NORWEGIAN BRIQUETTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORWEGIAN BRIQUETTING AS own?

NORWEGIAN BRIQUETTING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NORWEGIAN BRIQUETTING AS

Who owns NORWEGIAN BRIQUETTING AS?

FRODE AALTVEDT is the largest registered owner, with 100.0%.

What is the revenue of NORWEGIAN BRIQUETTING AS?

NORWEGIAN BRIQUETTING AS had revenue of NOK 0 in 2024.

Where is NORWEGIAN BRIQUETTING AS based?

NORWEGIAN BRIQUETTING AS has its business address in Porsgrunn.

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.