biztrac. BETA
COMPANY REGISTER PROFILE
831422432 ORG. NO. 2024 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

LYKKELIG BOLIG AS

Org. no. 831422432 Limited company (AS) Stjørdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 921,000
Equity NOK 238,000
Incorporated 2023
Share capital NOK 30,000

LYKKELIG BOLIG AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 831422432. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Oppføre boliger, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 921,000 in operating profit.

Former names: AFAS 040523-19 AS

Key figures · 2024

Revenue
NOK 5.2m
▲ +100 %
Operating profit
NOK 921,000
▲ +240 %
Equity
NOK 238,000
▲ +175 %
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
6.7%
Satisfactory
Return on total assets
Solidity
1.5%
Not satisfactory
Equity as a share of total capital

Who owns LYKKELIG BOLIG AS?

LYKKELIG BOLIG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYKKELIG BOLIG AS

Who owns LYKKELIG BOLIG AS?

BOLIGBYGGER1 AS is the largest registered owner, with 37.5%.

What is the revenue of LYKKELIG BOLIG AS?

LYKKELIG BOLIG AS had revenue of NOK 5.2m in 2024.

Who is the general manager of LYKKELIG BOLIG AS?

Mona-Lisa Drage Jacobsen is registered as general manager of LYKKELIG BOLIG AS.

Where is LYKKELIG BOLIG AS based?

LYKKELIG BOLIG AS has its business address in Stjørdal.

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.