BIZTRAC BETA
Uoppgitt

INHABIT AS

Org. no. 911978369 Limited company (AS) Lyngdal Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 60,000
Operating profit NOK 7,000
Equity NOK 58,000
Incorporated 2013
Share capital NOK 32,000

INHABIT AS is registered as a limited company in Lyngdal, Agder with organisation number 911978369. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2013. Registered share capital is NOK 32,000, divided into 32 shares. The company's stated purpose is: “Å eie, prosjektere og drive eiendomsvirksomhet, samt kjøp, salg og utleie av fast eiendom. Videre har selskapet som formål å drive håndverks- og byggtjenester, rådgivning, salg av varer og konsulenttjenester innenfor områdene, og virksomhet som måtte stå i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 60,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 60,000
Operating profit
NOK 7,000
Equity
NOK 58,000
Est. value
NOK 64,000

Financial health · 2025

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

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

Who owns INHABIT AS?

THOR INGE SVEINSVOLL
INHABIT AS
NOK 60,000 rev. · NOK 7,000 profit

INHABIT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INHABIT AS

Who owns INHABIT AS?

THOR INGE SVEINSVOLL is the largest registered owner, with 100.0%.

What is the revenue of INHABIT AS?

INHABIT AS had revenue of NOK 60,000 in 2025.

Who is the general manager of INHABIT AS?

Thor Inge Sveinsvoll is registered as general manager of INHABIT AS.

Where is INHABIT AS based?

INHABIT AS has its business address in Lyngdal.

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.