BIZTRAC BETA
Buying and selling of own real estate

RUDOLF & APPELBOM BOLIG AS

Org. no. 933874796 Limited company (AS) Tromsø Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 316,000
Operating profit NOK 165,000
Equity NOK 128,000
Incorporated 2024
Share capital NOK 1.0m

RUDOLF & APPELBOM BOLIG AS is registered as a limited company in Tromsø, Troms with organisation number 933874796. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Eie eller leie av egen fast eiendom, utvikling av bolig og annet som faller naturlig innenfor samme felt.”. The most recent filed accounts, for the 2024 financial year, show NOK 316,000 in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 316,000
Operating profit
NOK 165,000
Equity
NOK 128,000
Est. value
NOK 336,000

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.8%
Not satisfactory
Equity as a share of total capital

Who owns RUDOLF & APPELBOM BOLIG AS?

APPELBOM INVEST AS
RUDOLF & APPELBOM BOLIG AS
NOK 316,000 rev. · NOK 165,000 profit

RUDOLF & APPELBOM BOLIG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RUDOLF & APPELBOM BOLIG AS

Who owns RUDOLF & APPELBOM BOLIG AS?

APPELBOM INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of RUDOLF & APPELBOM BOLIG AS?

RUDOLF & APPELBOM BOLIG AS had revenue of NOK 316,000 in 2024.

Who is the general manager of RUDOLF & APPELBOM BOLIG AS?

Henrik Johan Larsen is registered as general manager of RUDOLF & APPELBOM BOLIG AS.

Where is RUDOLF & APPELBOM BOLIG AS based?

RUDOLF & APPELBOM BOLIG AS has its business address in Tromsø.

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.