biztrac. BETA
COMPANY REGISTER PROFILE
918770151 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Research and experimental development on natural sciences and engineering

DOGSAFE AS

Org. no. 918770151 Limited company (AS) Færder Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK −721,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−721k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

DOGSAFE AS is registered as a limited company in Færder, Vestfold with organisation number 918770151. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av sensorteknologi og andre produkter rettet mot dyr, og også konsulenttjenester innen ingeniørfaglig utvikling.”.

Former names: CIRENITA AS

Key figures · 2025

Operating profit
NOK −8,000
▲ +19 %
Equity
NOK −721,000
▼ −3 %
Est. value
NOK 17,000

Financial health · 2025

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.2%
Not satisfactory
Return on total assets
Solidity
-367.0%
Weak
Equity as a share of total capital

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

Who owns DOGSAFE AS?

DOGSAFE AS
· NOK −8,000 profit

DOGSAFE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DOGSAFE AS

Who owns DOGSAFE AS?

CIRENITA AS is the largest registered owner, with 66.0%.

Who is the general manager of DOGSAFE AS?

Kjersti Caroline Lønmo-Egeland is registered as general manager of DOGSAFE AS.

Where is DOGSAFE AS based?

DOGSAFE AS has its business address in Nøtterøy.

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.