BIZTRAC BETA
Development of building projects

DAMLIA B3 AS

Org. no. 918701796 Limited company (AS) Levanger Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −45,000
Equity NOK −3.0m
Incorporated 2017
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−45k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DAMLIA B3 AS is registered as a limited company in Levanger, Trøndelag with organisation number 918701796. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fremstilling/salg av eiendom og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −45,000
Equity
NOK −3.0m

Financial health · 2024

Liquidity
1035.48
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-41.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DAMLIA B3 AS?

NYBOLI INVEST AS
DAMLIA B3 AS
· NOK −45,000 profit

DAMLIA B3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAMLIA B3 AS

Who owns DAMLIA B3 AS?

NYBOLI INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of DAMLIA B3 AS?

Lars Hjelde is registered as general manager of DAMLIA B3 AS.

Where is DAMLIA B3 AS based?

DAMLIA B3 AS has its business address in Levanger.

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.