biztrac. BETA
COMPANY REGISTER PROFILE
934047990 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of trucks

BRIMSHOLM DRIFT AS

Org. no. 934047990 Limited company (AS) Bjørnafjorden Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 470,000
Operating profit NOK −326,000
Equity NOK 421,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−326k kr).

BRIMSHOLM DRIFT AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 934047990. The business is classified under rental and leasing of trucks (NACE 77.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg og utleie av maskiner og båter samt kjøp, drift og salg av eiendom og alt hva dermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 470,000 in revenue and NOK −326,000 in operating profit.

Key figures · 2025

Revenue
NOK 470,000
▲ +840 %
Operating profit
NOK −326,000
▼ −243 %
Equity
NOK 421,000
▼ −19 %
Est. value
NOK 605,000

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
-7.8%
Not satisfactory
Return on total assets
Solidity
10.6%
Satisfactory
Equity as a share of total capital

Who owns BRIMSHOLM DRIFT AS?

BRIMSHOLM DRIFT AS
NOK 470,000 rev. · NOK −326,000 profit

BRIMSHOLM DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRIMSHOLM DRIFT AS

Who owns BRIMSHOLM DRIFT AS?

BRIMSHOLM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRIMSHOLM DRIFT AS?

BRIMSHOLM DRIFT AS had revenue of NOK 470,000 in 2025.

Where is BRIMSHOLM DRIFT AS based?

BRIMSHOLM DRIFT AS has its business address in Lepsøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.