BIZTRAC BETA
Rental and operating of own or leased real estate

AKSVEIEN BOLIG AS

Org. no. 991092951 Limited company (AS) Larvik Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 960,000
Operating profit NOK 498,000
Equity NOK 3.4m
Incorporated 2007
Share capital NOK 100,000

Signals

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

AKSVEIEN BOLIG AS is registered as a limited company in Larvik, Vestfold with organisation number 991092951. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Kjøp/salg og utleie av faste eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 960,000 in revenue and NOK 498,000 in operating profit.

Key figures · 2024

Revenue
NOK 960,000
Operating profit
NOK 498,000
Equity
NOK 3.4m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns AKSVEIEN BOLIG AS?

MØLLERS HOLDING AS
AKSVEIEN BOLIG AS
NOK 960,000 rev. · NOK 498,000 profit

AKSVEIEN BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKSVEIEN BOLIG AS

Who owns AKSVEIEN BOLIG AS?

MØLLERS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AKSVEIEN BOLIG AS?

AKSVEIEN BOLIG AS had revenue of NOK 960,000 in 2024.

Who is the general manager of AKSVEIEN BOLIG AS?

Anders Møller is registered as general manager of AKSVEIEN BOLIG AS.

Where is AKSVEIEN BOLIG AS based?

AKSVEIEN BOLIG AS has its business address in Larvik.

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.