BIZTRAC BETA
Rental and operating of own or leased real estate

BEXRUD INVEST AS

Org. no. 980959147 Limited company (AS) Horten Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 948,000
Equity NOK 3.6m
Incorporated 1999
Share capital NOK 120,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BEXRUD INVEST AS is registered as a limited company in Horten, Vestfold with organisation number 980959147. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 120,000, divided into 240 shares. The company's stated purpose is: “Forvaltning av eiendom samt kjøp og salg av verdipapirer med tilhørende virksomhet”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 948,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 948,000
Equity
NOK 3.6m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns BEXRUD INVEST AS?

BEXRUD BIL AS
BEXRUD INVEST AS
NOK 1.4m rev. · NOK 948,000 profit

BEXRUD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEXRUD INVEST AS

Who owns BEXRUD INVEST AS?

BEXRUD BIL AS is the largest registered owner, with 100.0%.

What is the revenue of BEXRUD INVEST AS?

BEXRUD INVEST AS had revenue of NOK 1.4m in 2024.

Who is the general manager of BEXRUD INVEST AS?

Henning Bexrud is registered as general manager of BEXRUD INVEST AS.

Where is BEXRUD INVEST AS based?

BEXRUD INVEST AS has its business address in Horten.

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.