biztrac. BETA
COMPANY REGISTER PROFILE
932289709 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Technical testing and analysis

LIMPIDIUS AS

Org. no. 932289709 Limited company (AS) Strand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 611,000
Operating profit NOK −40,000
Equity NOK 167,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−40k kr).

LIMPIDIUS AS is registered as a limited company in Strand, Rogaland with organisation number 932289709. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Måling av inneklima og arbeidsmiljø. Kartlegging og risikovurdering av arbeidsmiljø.”. The most recent filed accounts, for the 2025 financial year, show NOK 611,000 in revenue and NOK −40,000 in operating profit.

Key figures · 2025

Revenue
NOK 611,000
▼ −6 %
Operating profit
NOK −40,000
▼ −134 %
Equity
NOK 167,000
▲ +4 %
Est. value
NOK 198,000

Financial health · 2025

Liquidity
3.39
Very good
Current assets ÷ current liabilities
Profitability
-17.8%
Not satisfactory
Return on total assets
Solidity
78.6%
Very good
Equity as a share of total capital

Who owns LIMPIDIUS AS?

LIMPIDIUS AS
NOK 611,000 rev. · NOK −40,000 profit

LIMPIDIUS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIMPIDIUS AS

Who owns LIMPIDIUS AS?

Gunnar Johnsen is the largest registered owner, with 50.0%.

What is the revenue of LIMPIDIUS AS?

LIMPIDIUS AS had revenue of NOK 611,000 in 2025.

Who is the general manager of LIMPIDIUS AS?

Gunnar Johnsen is registered as general manager of LIMPIDIUS AS.

Where is LIMPIDIUS AS based?

LIMPIDIUS AS has its business address in Jørpeland.

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.