BIZTRAC BETA
Freight transport by road

BRING FØR7 AS

Org. no. 827168572 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 215.7m
Operating profit NOK 4.0m
Equity NOK 2.7m
Incorporated 2021
Employees 15
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRING FØR7 AS is registered as a limited company in Oslo, Oslo with organisation number 827168572. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2021 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Transport og logistikkvirksomhet samt annen virksomhet som står i sammenheng med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 215.7m in revenue and NOK 4.0m in operating profit.

Key figures · 2024

Revenue
NOK 215.7m
Operating profit
NOK 4.0m
Equity
NOK 2.7m
Est. value
NOK 14.1m

Financial health · 2024

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.4%
Weak
Equity as a share of total capital

Who owns BRING FØR7 AS?

POSTEN BRING AS
BRING FØR7 AS
NOK 215.7m rev. · NOK 4.0m profit

BRING FØR7 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRING FØR7 AS

Who owns BRING FØR7 AS?

POSTEN BRING AS is the largest registered owner, with 100.0%.

What is the revenue of BRING FØR7 AS?

BRING FØR7 AS had revenue of NOK 215.7m in 2024.

Who is the general manager of BRING FØR7 AS?

Geir Inge Kirkestuen is registered as general manager of BRING FØR7 AS.

Where is BRING FØR7 AS based?

BRING FØR7 AS has its business address in Oslo.

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.